[
https://issues.apache.org/jira/browse/BOOKKEEPER-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690037#comment-13690037
]
Sijie Guo commented on BOOKKEEPER-629:
--------------------------------------
1. you don't need to change all the places that use addrToString. e.g.
RackawareEnsemblePlacementPolicy, parse ledger metadata.
2. create a default version of addrToString which uses ip. and just change the
places where you need to output the address using hostname as the issue
described. don't change other places if they are unrelated.
3. when you change cookie format (even cookie znode name), please consider
backward compatibility. otherwise, please keep it using ip before you had a
graceful solution for this part. similar comments applied on BookieIndexer.
4. you could parse useHostName flag in LedgerMetadata.serialize(boolean
useHostname) rather than change the the construct LedgerMetadata.
> 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: Improvement
> Components: 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
>
>
> 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
