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

Rakesh R commented on BOOKKEEPER-199:
-------------------------------------

Thanks Sijie for the comments & time:-) Yes, I will put the re-worked patch in 
the review board.

{quote}
1) in BookieWatcher, if a bookie server is restarted (maybe by admin guys) from 
R-O mode, seems there is no logic to remove a bookie from R-O mode to write 
mode. do I miss something?
{quote}
I am keeping the r-o status in bookie's presence znode(which is emphemeral), 
when restarting its creating new presence znode and like a normal r-w bookie.

{quote}
One thing might be missed is that when a force flushing (ledger eviction 
happened) failed, we might need to consider turning the bookie into R-O mode 
too.
{quote}
Hope you are pointing me to consider the ledger failures of 'SyncThread' ?

Also, I missed dealing the ledgerCache failures, it would be great to see your 
thoughts/opinion ?

Thanks,
Rakesh
                
> 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
>             Fix For: 4.1.0
>
>         Attachments: BOOKKEEPER-199.patch
>
>
> 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