[
https://issues.apache.org/jira/browse/BOOKKEEPER-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292739#comment-13292739
]
Uma Maheswara Rao G commented on BOOKKEEPER-180:
------------------------------------------------
@Sijie, I remeber we were discussing about strategy at that time.
{quote}
So how about make it as a strategy, user could decide shutting down or turning
to read-only when encountering a faulty bookie?
Sounds good to me.
Just adding config parameter for this option also should be ok. if we enable
it, Bookie will turn automatically to read-only mode. If we don't enable it, it
will sutdown by default. Admins also can start the bookie in read-only mode
explicitly.
{quote}
I think when user don't want read only mode to enable, then shutting down is
the other option.
You mean we will handle this conditions as part of BK-199?
> bookie server doesn't quit when running out of disk space
> ---------------------------------------------------------
>
> Key: BOOKKEEPER-180
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-180
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Ivan Kelly
> Fix For: 4.1.0
>
> Attachments: BK-180.diff, BK-180.diff_v2, BK-180.diff_v3,
> BK-180.diff_v4, conn3.png
>
>
> we found that the publish throughput drops down when one bookie server ran
> out of disk space (due to we don't do log rotation which exhausts disk
> space).
> did some investigation, we found that bookie server doesn't quit when
> encountering no disk space issue. so hub server treat this bookie server as
> available. The adding requests would be sent to this bookie server, some
> adding requests are put in journal queue to flush, but the journal flush
> thread has quit due to no disk space. so these adding requests didn't respond
> to bookie client until it read timeout and chose other bookie servers.
> we did an experiment to shut down the ran-out-of-disk-space bookie, the
> publish throughput went up again quickly.
--
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
