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

Flavio Junqueira commented on BOOKKEEPER-199:
---------------------------------------------

Hi Rakesh, The idea we had for BOOKKEEPER-201 was very simple. If we observe 
that the latency of writing to a given disk is high, then an operator can 
manually tell the bookie to stop creating ledgers on that disk. In the case 
that the bookie has multiple ledger devices available, it can slowly shift the 
traffic to the other devices.

The case of a broken disk is a bit more complicated. In this case, the best 
course of action I can see right now is to have an operator removing the bookie 
from the pool and executing a bookie recovery procedure for the ledger 
fragments on the dead disk.  

The cases you're mentioning are a bit different, since you can observe problems 
by catching exceptions, so you can automate the decision of removing the bookie 
from the pool. It sounds ok with me to do it.
                
> Provide bookie readonly mode, when journal/ledgers flushing has failed with 
> IOE
> -------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-199
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-199
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-server
>    Affects Versions: 4.0.0
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>            Priority: Critical
>
> Bookkeeper should change to readonly(r-o) mode when the journal/ledgers 
> flushing has failed with IOException. Later on, reject write requests on 
> server side and will accept only the read requests from the clients, because 
> even if flushing fails, the data in the bookie which has been flushed is 
> still valid.

--
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