[
https://issues.apache.org/jira/browse/BOOKKEEPER-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993557#comment-13993557
]
Rakesh R commented on BOOKKEEPER-629:
-------------------------------------
Thanks [~ikelly], IMHO we can push this improvement only to 4.3 branch and
resolve this JIRA now. If anyone feels to add into 4.2, we can backport it
after the admin tool to support IP change part. Does it make sense ?. Also one
more, this has been implemented on top of BOOKKEEPER-644, which is not there in
4.2 branch.
> Support hostname based ledger metadata to help users to change IP with
> existing installation
> --------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-629
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-629
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery, bookkeeper-client,
> bookkeeper-server
> Affects Versions: 4.2.1
> Reporter: Vinayakumar B
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments: 1-BOOKKEEPER-629.patch, 10-BOOKKEEPER-629.patch,
> 11-BOOKKEEPER-629.patch, 2-BOOKKEEPER-629.patch, 3-BOOKKEEPER-629.patch,
> 4-BOOKKEEPER-629.patch, 5-BOOKKEEPER-629.patch, 6-BOOKKEEPER-629.patch,
> 7-BOOKKEEPER-629.patch, 9-BOOKKEEPER-629.patch
>
>
> Register the bookie with *hostname:port* and also store the bookie addresses
> as *hostname:port* in ledger metadata files instead of *ip:port*
> This will help users to change the machine IP if they want without loosing
> their data.
> Supporting hostname based installation/functionality is one of the important
> requirement of users.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
