yzang commented on issue #266: Issue 265: Add persistable bookie status URL: https://github.com/apache/bookkeeper/pull/266#issuecomment-317842271 @sijie That make sense, I understand what you mean, but my concern is: Even if we persist the bookie status on disk, when we set the bookie to read only through http endpoint, the bookie will still be transitioned back to writable very quickly, because the DiskChecker runs periodically and would do the transition on each check, so there's no point setting the bookie to readonly on the fly, because the status still can't be persisted. I think we probably need a http endpoint that can set the bookie to forceReadOnly mode or cancel the forceReadOnly mode, so that we can choose to ignore any further transition operation. In order to do that, we need to persist this forceReadOnly option on disk, so that when the bookie get restarted, it should start with --readonly option. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
With regards, Apache Git Services
