[
https://issues.apache.org/jira/browse/BOOKKEEPER-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128244#comment-14128244
]
Rakesh R commented on BOOKKEEPER-773:
-------------------------------------
bq. If it is a blocker, then we should hold the release until this is in.
No, its not a blocker
bq.If this isn't a blocker and isn't ready for 4.3.0, why not push it to 4.4.0?
As we know, the feature is already checked in to 4.3.0. New bk installations
can make use of this. This tool is needed to update the cookie/ledgers and is
required for the existing installations. IMHO if we can reach to an agreement
will try push this in 4.3.0. Since it is not a new feature we can consider this
to 4.3.1?
I've uploaded new patch addressing Sijie's comments. Please have a look. Thanks!
> 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,
> 004-BOOKKEEPER-773-rename-bookieid.patch,
> 005-BOOKKEEPER-773-rename-bookieid.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.3.4#6332)
