[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433908#comment-13433908
 ] 

Rakesh R commented on BOOKKEEPER-246:
-------------------------------------

bq.connection loss is only kinda recoverable with zookeeper and you have to 
jump through hoops to do it, to ensure that the new handle has the same session 
etc. Generally, when ZK loses the connection, you're session is dead. And this 
is fine for us. When we get an exception like this we should error out to the 
top level and basically restart the recovery worker, as these have very little 
state which isn't dependent on zookeeper.

I agree the other modules should look at these kinda exceptions. Yeah, 
ReplicationWorker BOOKKEEPER-248 should consider these and have necessary 
cleanup logic.

+1 looks good to me and ready to go.
                
> Recording of underreplication of ledger entries
> -----------------------------------------------
>
>                 Key: BOOKKEEPER-246
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-246
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-client, bookkeeper-server
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-246.diff, BOOKKEEPER-246.diff, 
> BOOKKEEPER-246.diff, BOOKKEEPER-246.diff, BOOKKEEPER-246.diff
>
>
> This JIRA is to decide how to record that entries in a ledger are 
> underreplicated. 
> I think there is a common understanding (correct me if im wrong), that 
> rereplication can be broken into two logically distinct phases. A) Detection 
> of entry underreplication & B) Rereplication. 
> This subtask is to handle the interaction between these two stages. Stage B 
> needs to know what to rereplicate; how should Stage A inform it?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to