[
https://issues.apache.org/jira/browse/BOOKKEEPER-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151166#comment-14151166
]
Rakesh R commented on BOOKKEEPER-634:
-------------------------------------
bq.why couldn't me just print how many ledgers already are renamed?
Its good idea.
bq.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.
My bad, since I've used BK only with HDFS I always thinking in perspective of
HDFS, there the no: of ledgers are comparatively less. Going forward let me try
to understand more usecases.
How about making the number of concurrent operations configurable by adding a
'bandwidth' parameter(defaulting to 5 operations) - this will be maximum number
of ledgers which can be renamed simultaneously. If 6th operation comes, then it
will wait.
Does this sounds good to you? If agrees I'll try preparing a patch.
> 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)
