[
https://issues.apache.org/jira/browse/BOOKKEEPER-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998503#comment-13998503
]
Rakesh R commented on BOOKKEEPER-634:
-------------------------------------
Hi All,
*Proposal:*
+Pre-requisite+: Before bringing down the BK for upgradation admin has to
disable the AutoRecovery process
# How to update Cookies with hostname:
step-1) Set useHostNameAsBookieID=true in the config file
step-2) Call upgrade command, now this will regenerate the cookie with
hostname. This will be updated to both dirs and cookie znode(for example,
/ledgers/cookies/hostname:port) in ZK
step-3) Call finalize command, now this will delete the previous Cookie
znode(for example, /ledgers/cookies/ipaddress:port) from ZK.
# How to update ledger ensembles by replacing 'ipaddress' with 'hostname'
step-1) Exposing bookie shell command like,
metaupdate <currentBookieId> <toBookieId>
step-2) On invoking this command, BookKeeperAdmin will iterate over all the
ledgers, then update ledgermetadata and set data in ZK
I think writing clients will not get impacted because nowhere its comparing the
bookieIds(ipaddress/hostname). I have checked LedgerMetadata#isConflictWith()
implementation. Please point me if anything missing.
I've attached initial draft version, here considered only the ledger
metadata(urLedger is not done). If everyone agrees with this approach will
generate a new patch.
Welcome any comments.
Thanks,
Rakesh
> Provide admin tool to change bookie's identifier from IP to hostname
> --------------------------------------------------------------------
>
> 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
>
>
> This JIRA to discuss about admin tool for changing the bookie's IP to
> hostname.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
