leizhiyuan opened a new issue #3141:
URL: https://github.com/apache/bookkeeper/issues/3141


   **FEATURE REQUEST**
   
   when diskUsageThreshold is full, the bookie will convert to read-only 
   
   1. Please describe the feature you are requesting.
   
   ```
   
   
   readOnlyModeEnabled | If all ledger directories configured are full, then 
support only read requests for clients. If “readOnlyModeEnabled=true” then on 
all ledger disks full, bookie will be converted to read-only mode and serve 
only read requests. Otherwise the bookie will be shutdown. By default this will 
be disabled.
   -- | --
   
   
   
   diskUsageThreshold | For each ledger dir, maximum disk space which can be 
used. Default is 0.95f. i.e. 95% of disk can be used at most after which 
nothing will be written to that partition. If all ledger dir partions are full, 
then bookie will turn to readonly mode if ‘readOnlyModeEnabled=true’ is set, 
else it will shutdown. Valid values should be in between 0 and 1 (exclusive).
   -- | --
   
   
   ```
   
   now, if we have one disk, ledger dirs  are l1,l2,l3,l4 it runs ok
   
   but if we have two disks, one for l1,l2, the other for l3,l4, because of the 
difference of every entry, after run a long time, 
   
   the usage of disk1 will be 95%, but the other maybe 80%, then `DiskChecker` 
will think `If all ledger dir partions are full`  this is not true, they will 
write more date to disk, then disk 1 will be 100%, and goes down.
   
   
   
   3. Indicate the importance of this issue to you (blocker, must-have, 
should-have, nice-to-have).
      Are you currently using any workarounds to address this issue?
   
   should-have
   
   4. Provide any additional detail on your proposed use case for this feature.
   
   maybe the usage of any of the disk be 0.95, we can translate to read-only, 
or we can translate disk1 to read only, but disk2 can be written


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to