[
https://issues.apache.org/jira/browse/BOOKKEEPER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210164#comment-13210164
]
Ivan Kelly commented on BOOKKEEPER-160:
---------------------------------------
Hmm, I thought about this a bit, and the core problem is that Bookie has the
LedgerCache and LedgerDescriptors and the EntryLogger, which I think is wrong
and very tangled. There's no hierarchy which leads to the tight coupling
problem just observed. Bookie should only have access to the EntryLogger, and
the EntryLogger should own the LedgerDescriptors and LedgerCache. LedgerCache
should own the ledgerManager. etc.
This is a major refactor, and Im not suggesting we do it here. But I think it
does need to be done to make the code more maintainable.
> bookie server needs to do compaction over entry log files to reclaim disk
> space
> -------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-160
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-160
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Affects Versions: 4.0.0
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.1.0
>
> Attachments: BK-160.patch
>
>
> bookie server aggregates entries into entry log file. suppose there is lots
> of ledgers, each ledger has little messages. so a entry log file would
> contains messages from lots of different ledgers. if there is only one ledger
> not be deleted, the entry log file would not be removed, whose occupied disk
> space could not be reclaimed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
