[jira] [Closed] (BOOKKEEPER-899) Bookie should return to read-write mode once the disk usage drops before the threshold

["Matteo Merli (JIRA)" <ji...@apache.org>]

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

Matteo Merli closed BOOKKEEPER-899.
-----------------------------------

Closed as part of BookKeeper-4.4.0 release

> Bookie should return to read-write mode once the disk usage drops before the threshold
> --------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-899
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-899
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>    Affects Versions: 4.3.2
>            Reporter: Siddharth Sunil Boobna
>            Assignee: Siddharth Sunil Boobna
>             Fix For: 4.4.0
>
>
> Once a bookie goes above the diskUsageThreshold and becomes readOnly, it will never go back to readWrite even if the disk usage drops significantly.
> When the LedgerDirsMonitor gets a NoWritableLedgerDirException, it will put the bookie in read only mode, but will also stop monitoring and never goes back to read-write mode when the disk usage drops below threshold.
> Solution:
> The LedgerDirsMonitor thread should not break out of the while loop when it gets NoWritableLedgerDirException, and should continue monitoring the directories.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)