[
https://issues.apache.org/jira/browse/BOOKKEEPER-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094403#comment-14094403
]
Rakesh R commented on BOOKKEEPER-773:
-------------------------------------
bq.I forgot why we need to to do the two commands separately.
Ledger renaming can be done from any server but cookie updates needs to be
executed on each server as it has to update the filesystem directories. That
was my thoughts when proposing two separate commands. Now I could see a better
way of clubbing these two as a single command like below. Does this sounds good
?.
{code}
bkrename -useHostNameAsBookieId <true|false>
{code}
Sequence would be:
step-1. First update the cookie by following the same sequence discussed above
in this JIRA.
step-2. Then update the ledger metadata by following the sequence discussed in
BOOKKEEPER-634.
In both the steps, invert useHostNameAsBookieID flag value to get the previous
Bookieid.
> Provide admin tool to rename bookie identifier in Cookies
> ---------------------------------------------------------
>
> Key: BOOKKEEPER-773
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-773
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments: 001-BOOKKEEPER-773-rename-bookieid-in-cookies.patch,
> 002-BOOKKEEPER-773-rename-bookieid-in-cookies.patch,
> 003-BOOKKEEPER-773-rename-bookieid-in-cookies.patch
>
>
> The idea of this JIRA to implement a mechanism to efficiently rename the
> bookie identifier present in the Cookies. Cookie information will be present
> in:
> - ledger & journal directories in each Bookie server
> - cookies znode in ZooKeeper
--
This message was sent by Atlassian JIRA
(v6.2#6252)
