Flavio Paiva Junqueira updated ZOOKEEPER-356:

    Attachment: ZOOKEEPER-356.patch

There are three important parts to this patch:

# ''BookieHandle/BookieClient'': A BookieHandle has to guarantee that all 
requests either get a correct response from a bookie or they get errored out. 
In particular, it is important to guarantee that when the bookie corresponding 
to a BookieHandle crashes that it has no pending request in incomingQueue. In 
this patch, we call cleanQueue() to error out all requests and errorOut() on 
BookieClient to make sure again that all requests get a response;
# ''LedgerHandle'': This patch implements modifications to LedgerHandle that 
manipulate the ensemble according to observed failures. It changes the set of 
bookies over time, and writes to ZooKeeper when there has been a change to the 
# ''BookKeeper and LedgerManagementProcessor": When opening a ledger, we have 
to read the information on changes to the ensemble from ZooKeeper and set up 
all data structures to guarantee that we read entries from the correct set of 

> Masking bookie failure during writes to a ledger
> ------------------------------------------------
>                 Key: ZOOKEEPER-356
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-356
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: contrib-bookkeeper
>            Reporter: Flavio Paiva Junqueira
>            Assignee: Flavio Paiva Junqueira
>             Fix For: 3.2.0
>         Attachments: ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, 
> ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, 
> The idea of this jira is to work out the changes necessary to make a client 
> mask the failure of a bookie while writing to a ledger. I'm submitting a 
> preliminary patch, but before I submit a final one, I need to have 288 
> committed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to