[
https://issues.apache.org/jira/browse/BOOKKEEPER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400565#comment-13400565
]
Uma Maheswara Rao G commented on BOOKKEEPER-315:
------------------------------------------------
Actually this point is a Review comment in BOOKKEEPER-299 from Ivan.
[See my analysis comment |
https://issues.apache.org/jira/browse/BOOKKEEPER-299?focusedCommentId=13400393&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13400393]
I am thinking currently, Call backs can be there as a chain from Ledger to
Frgment and Feragment to Entry. At the stage of entry we can think for making
it one by one.
> Ledger entries should be replicated sequentially instead of parallel.
> ---------------------------------------------------------------------
>
> Key: BOOKKEEPER-315
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-315
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client
> Affects Versions: 4.2.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
>
> Currently BookKeeperAdmin will copy the entries parallel.
> This may create more load on the servers. To avoid that, we can refactor the
> BKAdmin code to copy the entries sequential.
--
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
