[GitHub] [bookkeeper] wangjialing218 commented on pull request #3248: Support set local region for RegionAwareEnsemblePlacementPolicy

[GitBox <gi...@apache.org>]

wangjialing218 commented on PR #3248:
URL: https://github.com/apache/bookkeeper/pull/3248#issuecomment-1378178982

   > What alternative solutions have you looked at?
   
   In synchronous geo-replication solution, suppose we have 4 bookies in two regions, bk1 and bk2 with rack setting `/region1/rack`, bk3 and bk4 with rack setting `/region2/rack`。
   A broker in region1 need to read ledger data and the writeSet is {bk1,bk3}, it's better to let broker read from bk1 which is in same region to avoid across region tracffic. If the topic unloaded to another broker in region2, the broker could read ledger data from bk3 instead.
   
   > AFACT, the dummy bookie node is created to make use of the resolver API that takes BookieNode as a parameter. After that it goes through the same resolution mechanism as any bookie; so if you use script-based mapping you can update it to resolve the client's address to region/rack etc, it does not really matter if the client is co-hosted with a bookie.
   
   It's okey to resolve the broker's address to region/rack to achieve, we need to configure the resolver and it's not an easy way if brokers deployed in kubernetes.
   This PR provide a  bookkeeper client configuration `reppLocalRegion` for broker, so we could add region-aware setting for each broker according to where the broker is placement by command or configuration. 


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org