[
https://issues.apache.org/jira/browse/BOOKKEEPER-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152886#comment-14152886
]
Rakesh R commented on BOOKKEEPER-634:
-------------------------------------
Thank you for the patience. I'd like to do an attempt tonight and hope for a
better one.
I'm planning to incorporate the following changes:
# modify the command format like below, this is to make the command usage
similar to the 'updatecookie'
{code}
updateledger -bookieId <hostname|ip> [-batchsize N] [-limit N]
{code}
# print the number of ledgers renamed to know the progress.
# use iterator and do update by iterating the ledgers batch by batch(bandwidth
I'm calling as batchsize). Ledgers present in each batch will be executed
concurrently. After completing all the ledgers in the current batch, it will
iterate and collect items for the next batch. This cycle will continue. Default
value is 5. Also, to avoid overwhelm the system, user can define the total
number of ledgers to be considered. Say, if limit=100, it will exit when the
successfully renamed ledger count becomes 100. By default this will be
Integer.MAX. This is just a draft idea, when preparing a patch will get more
clarity.
> Provide admin tool to rename bookie identifier in ledger metadata
> -----------------------------------------------------------------
>
> Key: BOOKKEEPER-634
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-634
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server
> Affects Versions: 4.2.1
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments: 0001-BOOKKEEPER-634-initial-draft-version.patch,
> 001-BOOKKEEPER-634-rename-bookieid-in-ledger.patch,
> BOOKKEEPER-634-rename-bookieid-in-ledger.patch, BOOKKEEPER-634.patch,
> BOOKKEEPER-634.patch
>
>
> This JIRA to discuss about admin tool for changing the bookie's IP to
> hostname.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
