[
https://issues.apache.org/jira/browse/BOOKKEEPER-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430380#comment-13430380
]
Sijie Guo commented on BOOKKEEPER-191:
--------------------------------------
@Ivan
ChangeLedgerOp is asynchronous op, but PersisteOp is synchronous op. so when
the ChangeLedgerOp is executing, the previous persist ops might be still
on-the-fly. so doChangeLedger is to avoid close ledger until all previous
requests are finished. then it is safe to change ledger.
> Hub server should change ledger to write, so consumed messages have chance to
> be garbage collected.
> ---------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-191
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-191
> Project: Bookkeeper
> Issue Type: Improvement
> Affects Versions: 4.1.0
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.2.0
>
> Attachments: BK-191.diff, BOOKKEEPER-191.diff, BOOKKEEPER-191.diff
>
>
> currently, hub server write entries to only one ledger, if a topic doesn't
> change ownership, all entries will be added to this ledger. so those consumed
> messages don't have chance to be garbage collected.
--
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
