[
https://issues.apache.org/jira/browse/BOOKKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261416#comment-13261416
]
Flavio Junqueira commented on BOOKKEEPER-220:
---------------------------------------------
# My point is simply that it would be good to not try to re-implement hedwig
with different terminology. The concept of Managed Ledger seems pretty close to
the one of a Topic for hedwig, but so far ML feels like a subset. If it is
subset then great, we might be even able to implement hedwig hubs more easily
with MLs. I actually think it would be good to try to write down the
differences at the abstract level. Looking at the hedwig code might not be the
best thing to do at this point.
# One option might be to rely on the password scheme we have. If a bookie
receives an add entry request with the wrong master key (generated from the
password), then it returns an error. The client may decide at that point that
it is not the writer of the ML.
# Sure, I understand this is work in progress, I just wanted to make sure to
have my comment written down.
I was also wondering if it would make sense to implement queue semantics for
MLs. In your current design, all readers read all messages if I understand it
right. Do you think it makes sense?
> Managed Ledger proposal
> -----------------------
>
> Key: BOOKKEEPER-220
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-220
> Project: Bookkeeper
> Issue Type: New Feature
> Components: bookkeeper-client
> Reporter: Matteo Merli
> Assignee: Matteo Merli
>
> The ManagedLedger design is based on our need to manage a set of ledgers,
> with a single writer (at any point in time) and a set on consumers that read
> entries from it.
> The ManagedLedger also takes care of periodically closing ledgers to have a
> "reasonable" sized sets of ledgers that can individually deleted when no more
> needed.
> I've put on github the interface proposal (along with an early WIP
> implementation)
> http://github.com/merlimat/managed-ledger
--
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
