[
https://issues.apache.org/jira/browse/BOOKKEEPER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442903#comment-13442903
]
Uma Maheswara Rao G commented on BOOKKEEPER-304:
------------------------------------------------
{quote}
However, I wanted to get the base case committed first, and then optimize
after.
{quote}
Completely make sense, especially when building some big features.
Also, Wanted to make a note that, we are planning to keep the auditor as
separate process now right. So, it should not create issues for the BK
instances. We can optimize one by one for considering this new process loads.
@Sijie, Your thought is good on memory optimizations. Yes, if you find out any
such improvements in this new area of code, even its committed, please file a
JIRAs under BK-237. We can attack one by one. Thanks a lot for your comments.
> Prepare bookie vs ledgers cache and will be used by the Auditor
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-304
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-304
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Affects Versions: 4.2.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-304.1.patch, BOOKKEEPER-304.2.patch,
> BOOKKEEPER-304.2.patch, BOOKKEEPER-304.3.patch, BOOKKEEPER-304.4.patch,
> BOOKKEEPER-304.5.patch, BOOKKEEPER-304.diff
>
>
> This JIRA discusses how to build bookie -> ledgers cache and this will be
> used by the Auditor to publish the suspected ledgers of failed bookies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
