zymap commented on PR #4225: URL: https://github.com/apache/bookkeeper/pull/4225#issuecomment-1984945236
For the first case, I think if you start bookie with readonly, the bookie will in forceReadonly and won't be writable anymore. So even if the disk has space and it won't transition to the write mode. For the third case, yes. It is very difficult to know if it is controlled by the rest API or the disk threshold for now. So if you want to make bookie into readonly forever, you need to make it to the forceReadonly, not the readonly state. So i think it should be acceptable? -- 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]
