[
https://issues.apache.org/jira/browse/BOOKKEEPER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456924#comment-13456924
]
Uma Maheswara Rao G commented on BOOKKEEPER-315:
------------------------------------------------
Attached a patch with the batching approach with out modifying much to BKAdmin
older functionality side.
Whole refactoring also I did, But it turns to me that huge changes. So, I felt,
that should not be the target now, as we concerned mainly about auto
replication part as that will run automatically and should not put more load on
other servers due replication work.
Also added a config item maxAllowedEntriesPerFragmentInRereplication (can
suggest better name)
Added 2 tests to check that this changes does not effect any fuctionality.
Please take a look and give me your opinion on this.
Thanks
Uma
> 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-auto-recovery, bookkeeper-client
> Affects Versions: 4.2.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Attachments: BOOKKEEPER-315.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
