[
https://issues.apache.org/jira/browse/BOOKKEEPER-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990972#comment-13990972
]
Rakesh R commented on BOOKKEEPER-629:
-------------------------------------
I could see one case, where the "BookieMetadataFormatVersion" will be
incremented inorder to change IP to hostname. Now old clients may fail in
parsing the metadata LedgerMetadata#parseConfig (). Here to avoid parsing err
before running the tool, admin should ensure all the clients also be upgraded
to 4.3.0
[~fpj] If we can reach to an agreement like, all the meta changes will do only
through admin tool, then will try push this JIRA in and will start focusing on
the admin tool BOOKKEEPER-634. Does that make sense to you ?
> 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)
