[
https://issues.apache.org/jira/browse/BOOKKEEPER-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-175:
----------------------------------
Attachment: BOOKKEEPER-175.diff
Patch moves handle creation out of bookie. There are now two types of handle,
LedgerDescriptorImpl and LedgerDescriptorReadOnlyImpl. Any attempt to use the
read only version for writing will throw an exception. This should make
implementing BOOKKEEPER-135 (check passwd on fencing) trivial.
> Bookie code is very coupled
> ---------------------------
>
> Key: BOOKKEEPER-175
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-175
> Project: Bookkeeper
> Issue Type: Improvement
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.1.0
>
> Attachments: BOOKKEEPER-175.diff
>
>
> Bookie owns EntryLogger, LedgerCache, LedgerDescriptors which all depend on
> each other in strange ways. Sometimes we access the ledgerCache directly,
> sometimes through LedgerDescriptors. etc, etc. It's messy and there's no
> hierarchy.
> I propose that we refactor Bookie to only contain the EntryLogger and
> journalling code (this should be factored at some stage also). The
> EntryLogger can then own the ledgerCache and the LedgerDescriptors, and then
> we would how have to have the entanglement as observed on BOOKKEEPER-160.
--
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
