[
https://issues.apache.org/jira/browse/BOOKKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262177#comment-13262177
]
Matteo Merli commented on BOOKKEEPER-220:
-----------------------------------------
# How should we proceed on this? Who is going to list the Hedwig differences
from ML? I am perfectly fine in extending the ML subset to something that can
be convenient to both us and Hedwig. So far I just included the minimal set of
requirements that we identified. Also, I am perfectly ok in changing any
terminology used for the ML.
# I don't know how the passord/master-key work in BK, need to dig more into it.
So far, I just made that you can choose the password for the entire ML. The
same password will be used when opening ledgers for reading/writing.
Right now, if 2 different clients try to open the same ML and start writing,
they will write into different BK ledgers, and possibly corrupt the ML state.
Same thing for reading, if ML is running on 2 boxes, the cursor list will not
be accurate leading to wrong ledgers deletions.
I think the password have to be the same (within the same ML), because
ledgers created on one box will need to be read from others in case of a
failover.
# Ok
# Queue semantics: the original idea was to leave the topic/queue
implementation in the broker/hub layer. In this case, when the broker wants to
use the ML for a queue, it will simply use one single cursor. Again, if it
makes sense we could possibly move that code into the ML.
> 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
