[
https://issues.apache.org/jira/browse/BOOKKEEPER-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697152#comment-13697152
]
Sijie Guo commented on BOOKKEEPER-629:
--------------------------------------
several concerns of UUID:
1. the backward compatibility issue? how an old bookie client interacts with
new bookies registered with UUID?
2. if you change the ledger metadata to use UUID rather than 'hostname:port',
how to keep backward compatibility issue? if you don't change the ledger
metadata to use UUDI, you are still facing the problem of changing hostname or
IP.
In general, the bookie host is already kind of identifier (UUID) in cookie
file. I don't think we need a separated uuid field. the changing of the
environment should be counted as a bookie upgrade and addressed in
BOOKKEEPER-634. I don't think this is a big deal.
> 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
