Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 8 Aug 2017 11:46:00 +0000 (UTC)
From: "Andrew Mashenkov (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.13093139.1502192746000.116726.1502192760373@Atlassian.JIRA>
In-Reply-To: <JIRA.13093139.1502192746000@Atlassian.JIRA>
References: <JIRA.13093139.1502192746000@Atlassian.JIRA> <JIRA.13093139.1502192746307@jira-lw-us.apache.org>
Subject: [jira] [Created] (IGNITE-5986) Fix failed test in .NET suite.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 08 Aug 2017 11:46:04 -0000

Andrew Mashenkov created IGNITE-5986:
----------------------------------------

             Summary: Fix failed test in .NET suite.
                 Key: IGNITE-5986
                 URL: https://issues.apache.org/jira/browse/IGNITE-5986
             Project: Ignite
          Issue Type: Test
          Components: cache, platforms
    Affects Versions: 2.1
            Reporter: Andrew Mashenkov
             Fix For: 2.2


Preface:
I've found we use closeQuiet() method in LuceneIndex.close() that suppress exceptions. 
So, this is why we have no issues here before.

I'd think when index is closing, it is expected that all queries being cancelled and at the moment all QueryCursors (which use IndexReaders) has been closed already.
But I' observe it is not true in some cases.

Looking at GridCacheProcessor.stopCache() method we call onCacheStop()-> unregisterCache -> table.onDrop() -> luceneIdx.close().

Looks like someone forget to close Cursor or\and Cursor wasn't closed during query cancelation.

We have to investigate this and 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)