You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Barry Oglesby (JIRA)" <ji...@apache.org> on 2017/04/05 01:51:41 UTC

[jira] [Resolved] (GEODE-2750) Lucene destroy index should destroy the index on remote members before destroying it in the local member

     [ https://issues.apache.org/jira/browse/GEODE-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barry Oglesby resolved GEODE-2750.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0

> Lucene destroy index should destroy the index on remote members before destroying it in the local member
> --------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-2750
>                 URL: https://issues.apache.org/jira/browse/GEODE-2750
>             Project: Geode
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Barry Oglesby
>             Fix For: 1.2.0
>
>
> Destroying the AsyncEventQueue is partially a local and partially a distributed operation. The local part is the stopping and destroying the actual AsyncEventQueue and GatewaySender instances. Also, removing the AsyncEventQueue id from the data Region. The distributed part is the underlying co-located AsyncEventQueue  and fileAndChunk PartitionedRegions. Co-located PRs cannot be locally destroyed, so they have to be distributed destroys.
> Destroying the local parts of the index in remote members first followed by the local parts in the initiating member and finally the co-located regions should help with RegionDestroyedExceptions occurring when regions are destroyed out from under the index.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)