eolivelli opened a new issue #2396:
URL: https://github.com/apache/bookkeeper/issues/2396
**BP**
This is the master ticket for tracking BP-41: Separate BookieId from Bookie
Network Address
We want to separate the concepts of BookieId from BookieSocketAddress.
Currently (up to 4.11.x) there is a too strict coupling from the ID of a
Bookie and its location:
- We are storing BookieSocketAddresses (simply a hostname:port or ip:port
pair) into Ledger Metadata
- The Identity of a bookie is bound to the network address of the primary
endpoint of the Bookie ('bookie-rpc' endpoint in term of BP-38)
This fact is very awkward, because:
- you cannot change the network address of a Bookie
- you cannot use a custom Id for the bookie, something that would be more
useful in the context of the deployment of the bookie
The proposal will run thru this problems and it will propose to separate the
concept of BookieId from BookieSocketAddress.
The implementation will be divided in two separate works:
- client side changes: drop BookieSocketAddress from LedgerMetadata and use
BookieId in EnsemblePlacemenetPolicies
- bookie side changes: allow to configure a store a BookieId that is
independent from the current BookieSocketAddress
Proposal PR - #abc
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
