[
https://issues.apache.org/jira/browse/BOOKKEEPER-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433370#comment-13433370
]
Uma Maheswara Rao G commented on BOOKKEEPER-246:
------------------------------------------------
Ivan,
But they are 2 different category of exceptions right?
{quote}
Recoverable errors: the disconnected event, connection timed out, and the
connection loss exception are examples of recoverable errors, they indicate a
problem that happened, but the ZooKeeper handle is still valid and future
operations will succeed once the ZooKeeper library can reestablish its
connection to ZooKeeper.
Fatal errors: the ZooKeeper handle has become invalid. This can be due to an
explicit close, authentication errors, or session expiration.
{quote}
connection loss is recoverable error right. We can reuse the zk handle as it is
still valid. I am not sure, whether I am missing something from your point of
view :(.
> 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
