[ https://issues.apache.org/jira/browse/BOOKKEEPER-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991552#comment-13991552 ]
Sijie Guo commented on BOOKKEEPER-629: -------------------------------------- wait, I don't understand here, why you need to bump 'BookieMetadataFormatVersion'? InetSocketAddress works for both IP and hostname. > 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)