Github user reddycharan commented on the issue:
https://github.com/apache/bookkeeper/pull/81
@sijie ok, it is bit of an extreme case for it to happen (since
BookieStorageThreshold will be generally configured at safe levels) and even in
the case of eventuality (by misconfiguring or when bookie receives very high
traffic before next DISK_CHECK during the DISK_CHECK_INTERVAL), we should be ok
to lose a bookie because of write quorum.
Being said that, I don't have a strong reason to say no for providing extra
safety mechanism / recoverability option. It should be ok, but we have to work
on conflicts.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
