Mailing-List: contact dev-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Wed, 1 Feb 2017 20:15:51 +0000 (UTC)
From: "nabarun (JIRA)" <jira@apache.org>
To: dev@geode.apache.org
Message-ID: <JIRA.13039557.1485975677000.10632.1485980151620@Atlassian.JIRA>
In-Reply-To: <JIRA.13039557.1485975677000@Atlassian.JIRA>
References: <JIRA.13039557.1485975677000@Atlassian.JIRA> <JIRA.13039557.1485975677384@jira-lw-us.apache.org>
Subject: [jira] [Updated] (GEODE-2410) afterPrimary and afterSecondary event
 listeners pass through the same critical section
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Feb 2017 20:16:12 -0000


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

nabarun updated GEODE-2410:
---------------------------
    Description: 
* afterPrimary and afterSecondary listeners will call the same critical section.
* They will acquire a Dlock on the bucket and create the index if primary.
* If they are secondary it will close the writer and release the Dlock.
* The primary will reattempt to acquire the lock after 5seconds and continue to loop as long as it is still primary.


  was:
* afterPrimary and afterSecondary listeners will call the same critical section.
* They will acquire a Dlock on the bucket and create the index if primary.
* If they are secondary it will close the writer and release the Dlock.
* The primary will reattempt to acquire the lock after 54 seconds and continue to loop as long as it is still primary.


> afterPrimary and afterSecondary event listeners pass through the same critical section
> --------------------------------------------------------------------------------------
>
>                 Key: GEODE-2410
>                 URL: https://issues.apache.org/jira/browse/GEODE-2410
>             Project: Geode
>          Issue Type: Bug
>          Components: lucene
>            Reporter: nabarun
>
> * afterPrimary and afterSecondary listeners will call the same critical section.
> * They will acquire a Dlock on the bucket and create the index if primary.
> * If they are secondary it will close the writer and release the Dlock.
> * The primary will reattempt to acquire the lock after 5seconds and continue to loop as long as it is still primary.


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