[jira] [Updated] (BOOKKEEPER-180) bookie server doesn't quit when running out of disk space

["Sijie Guo (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sijie Guo updated BOOKKEEPER-180:
---------------------------------

    Attachment: conn3.png

attach a throughput graph. the throughput went down when a bookie ran out of disk space, while the throughput went up again after shutting down the ran-out-of-disk-space bookie server.
                
> 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
>             Fix For: 4.1.0
>
>         Attachments: 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