[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416122#comment-13416122
]
Rakesh R commented on BOOKKEEPER-199:
-------------------------------------
Thanks Sijie.
bq.Is the utility a separated tool that admin guys could run to check disk?
Which scenarios it would be used?
I've just thought of separating the disk checking logic. This has sort of
useful apis which EntryLogger and LedgerCache will be using. (if we have a
usecase, will expose in admin also)
bq.so if did it in this way, I think there is no changes in bookie client. we
just need to change bookie server to do action when encountering too many
IOExceptions:
Here, I just thought of bkclient behaviours: when reading it should have logic
to find the r-o bookies and able to serve the read request. While writing these
bookies will be masked and will not be available.
bq.1) and 2) could be set as a configuration setting to let user decide what to
do, which I called it as strategy as previous comment.
Yeah exactly, its configurable and how about exposing config item
'readonlyModeEnabled=false' in bk_server.conf?
bq.so we need a separated znode to hold all r-o bookies for tracking.
Yes, I agree with Flavio's suggestion to delete the ephemeral znode so that
admin will be able to know about the faulty bookie and can act upon.
How about providing a separate znode like
'/ledgerrootpath/available/readonly/'....This 'readonly' persistent znode
contains list of bookies represented as (IP:PORT) ephemeral znodes once the
bookie marked as readonly.
> 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: Bug
> Components: bookkeeper-server
> Affects Versions: 4.0.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Priority: Critical
> Fix For: 4.2.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
