We can defer this to 4.5. As mentioned in Jira issue is spurious wake ups. On Sunday, April 24, 2016, Sijie Guo (JIRA) <[email protected]> wrote:
> > [ > https://issues.apache.org/jira/browse/BOOKKEEPER-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255751#comment-15255751 > ] > > Sijie Guo commented on BOOKKEEPER-924: > -------------------------------------- > > [~jujjuri] what is the impact of this issue? It is a bit unclear to me > what is fixed and why changing it to countdownlatch. and shall this jira is > marked to be 4.4.0. > > > addEntry() is susceptible to spurious wakeups > > --------------------------------------------- > > > > Key: BOOKKEEPER-924 > > URL: > https://issues.apache.org/jira/browse/BOOKKEEPER-924 > > Project: Bookkeeper > > Issue Type: Bug > > Affects Versions: 4.3.2 > > Reporter: Venkateswararao Jujjuri (JV) > > Assignee: Venkateswararao Jujjuri (JV) > > Priority: Critical > > Fix For: 4.4.0 > > > > > > LedgerHandle sync interface heavily depends on SyncCounter to convert > async interfaces > > into sync interfaces. > > Usaylly > > SyncCounter.inc() > > asyncCall() > > SyncCOunter.block(0) > > The block code is. > > synchronized void block(int limit) throws InterruptedException { > > while (i > limit) { > > int prev = i; > > wait(); > > if (i == prev) { > > break; > > } > > } > > } > > Since 'i' is going to be same as 'prev' on spurious wakeup, and wait() > can return on spurious wakeups. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > -- Sent from iPhone
