[
https://issues.apache.org/jira/browse/BOOKKEEPER-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453921#comment-13453921
]
Sijie Guo commented on BOOKKEEPER-401:
--------------------------------------
If I remembered correctly, we only 'unsetSuccessAndSendWriteRequest' to new
selected bookie after succeed to write ensemble info to ZooKeeper. which means
we won't acked an add before the metadata persisted in ZooKeeper.
Do you encounter such issue? Is there any log about it?
> LedgerHandle should not ack entries till an ensemble change has been
> persisted to Zookeeper
> -------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-401
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-401
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Reporter: Aniruddha
>
> Consider the following case:
> Ensemble is A, B, C
> It changes to A, B, D locally and an update to write to ZK is in progress.
> We get a write request that writes to this ensemble, receives responses and
> acks back a success.
> The ensemble write to zk fails. We've acked an add for which there is no
> information in zookeeper.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
