[
https://issues.apache.org/jira/browse/BOOKKEEPER-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186749#comment-15186749
]
ASF GitHub Bot commented on BOOKKEEPER-895:
-------------------------------------------
GitHub user sboobna opened a pull request:
https://github.com/apache/bookkeeper/pull/25
BOOKKEEPER-895: GC ledgers that are no longer a part of the ensemble
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sboobna/bookkeeper BOOKKEEPER-895
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bookkeeper/pull/25.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #25
----
commit 82ddaf2f4ce2e209eb6088dd1b8f75e258d445fc
Author: Siddharth Boobna <[email protected]>
Date: 2016-02-11T18:20:36Z
BOOKKEEPER-895: GC ledgers that are no longer a part of the ensemble
Change-Id: I3f74e09162f9a1116dd47a19262923ced940b7f2
----
> bookies should not retain ledgers which no longer belong to them
> ----------------------------------------------------------------
>
> Key: BOOKKEEPER-895
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-895
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Affects Versions: 4.3.2
> Reporter: Siddharth Sunil Boobna
> Assignee: Siddharth Sunil Boobna
>
> The bookies do not clean up ledgers on their disk which exist in zookeeper
> but are not assigned to them by the ensemble definition. This happens if a
> bookie has a ledger, went offline, it was replicated elsewhere, and then the
> bookie comes back up. Then we have an extra copy of the same ledger.
> Solution:
> Bookie should handle this case in the garbage collector. Since we will have
> to read the ledger metadata and go through its ensemble set to determine if
> the bookie exists in the ensemble, this is an expensive operation. Thus, we
> will only run this task once every day.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
