You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Enrico Olivelli (JIRA)" <ji...@apache.org> on 2015/09/23 08:53:04 UTC

[jira] [Updated] (BOOKKEEPER-875) Provide a configuration option to set a fixed BookieID

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enrico Olivelli updated BOOKKEEPER-875:
---------------------------------------
    Description: 
In Bookkeeper 4.3.x there are two ways of configuring the BookieID, that is using an IP address or using the hostname (useHostNameAsBookieID). There is also an option to force the use of a specific network interface.

In environments with many IP addresses both of the two options can lead to an undeterministic behaviour.

Another useful option would be to set explicitly a "BookieID".
I have to usecases:
- network configuration of the machine changes, but I want to preserve bookie data without recovery
- bookie data is to be moved to another machine (that is somehow similar the the first case)

  was:
In Bookkeeper 4.3.x there are two ways of configuring the BookieID, that is using an IP address or using the hostname (useHostNameAsBookieID). There is also an option to force the use of a specific network interface.

In environments with many IP addresses both the two option can lead to an undeterministic behaviour.

Another useful option would be to set explicitly a "BookieID".
I have to usecases:
- network configuration of the machine changes, but I want to preserve bookie data without recovery
- bookie data is to be moved to another machine (that is somehow similar the the first case)


> Provide a configuration option to set a fixed BookieID
> ------------------------------------------------------
>
>                 Key: BOOKKEEPER-875
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-875
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>    Affects Versions: 4.3.0
>            Reporter: Enrico Olivelli
>            Priority: Critical
>
> In Bookkeeper 4.3.x there are two ways of configuring the BookieID, that is using an IP address or using the hostname (useHostNameAsBookieID). There is also an option to force the use of a specific network interface.
> In environments with many IP addresses both of the two options can lead to an undeterministic behaviour.
> Another useful option would be to set explicitly a "BookieID".
> I have to usecases:
> - network configuration of the machine changes, but I want to preserve bookie data without recovery
> - bookie data is to be moved to another machine (that is somehow similar the the first case)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)