[
https://issues.apache.org/jira/browse/BOOKKEEPER-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697640#comment-13697640
]
Rakesh R commented on BOOKKEEPER-629:
-------------------------------------
Sorry, please ignore the above example, its not correct.
So if I understand correctly, here the idea is to keep the identifier as
'hostname:port' format. For example, one bookie starts with the id
'HOST-10-18-40-30:8020', when user change the hostname to 'HOST-10-18-40-35',
this bookie will publish 'HOST-10-18-40-30:8020' and content as the actual
'HOST-10-18-40-35:8020'. Here I could see one conflicts, say when a new bookie
wants to joins with its actual hostname as 'HOST-10-18-40-30' and port 8020, he
will get ZNodeExistsException.
> Support hostname based ledger metadata to help users to change IP with
> exitsting 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, 4.3.0
> Reporter: Vinay
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments: 1-BOOKKEEPER-629.patch, 2-BOOKKEEPER-629.patch,
> 3-BOOKKEEPER-629.patch, 4-BOOKKEEPER-629.patch, 5-BOOKKEEPER-629.patch,
> 6-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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
