[
https://issues.apache.org/jira/browse/BOOKKEEPER-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149685#comment-14149685
]
Sijie Guo commented on BOOKKEEPER-634:
--------------------------------------
let's stick on renaming bookie identifier on ledger metadata here.
-1 on getting all ledgers just for counting the total number of ledgers, it is
not good for a real production use case. And it doesn't make sense to add an
API to get a count in prior to renaming, since ledger is adding and deleting
all the time. so instead of printing percentage of progress, why couldn't me
just print how many ledgers already are renamed?
I didn't say the we need to rename in sequence. what I pointed out in my
comments again and again, is that you should think of a real production system,
you should limit the concurrency of ledger metadata access, to not overwhelm
the system.
-1 from me if these two points couldn't be addressed.
> 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)
