[
https://issues.apache.org/jira/browse/BOOKKEEPER-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047169#comment-16047169
]
ASF GitHub Bot commented on BOOKKEEPER-753:
-------------------------------------------
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.
> Bookie should run garbage collection before startup when all directories
> became full
> ------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-753
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-753
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.5.0
>
>
> otherwise, a bookie that ran-out-of disk would never be started up again.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
