+1 (non-binding) At least combined with the current features of bookkeeper, readOnlyModeOnAnyDiskFullEnabled should be enabled by default. If a single disk is full and it is not switched to read-only, the writeCache will only make the situation worse as the amount increases.
On Sat, Nov 16, 2024 at 11:56 PM xiangying meng <xiangy...@apache.org> wrote: > Dear Bookkeeper Community, > > I hope this message finds you well. I would like to bring to your > attention a proposal to change the default value of the > `readOnlyModeOnAnyDiskFullEnabled` feature to true in Apache > Bookkeeper. > > In our practical experience, converting a bookie to Read Only mode > when any ledger disk is full is crucial. Without this change, a full > bookie disk results in numerous message failures while attempting to > write to the ledger disk. Additionally, since the bookie's status > remains available, no alarms are triggered for maintenance personnel, > leading to delays in response. > > This feature was introduced in [PR > #3212](https://github.com/apache/bookkeeper/pull/3212) and has proved > to be stable over time. We believe it is safe and beneficial to enable > this feature by default. > > Please feel free to share your thoughts or concerns regarding this change. > > Best regards, > > Xiangying Meng >
