You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bookkeeper.apache.org by "wenbingshen (via GitHub)" <gi...@apache.org> on 2023/01/30 13:01:57 UTC

[GitHub] [bookkeeper] wenbingshen commented on pull request #3721: New ensemble choose different rack first.

wenbingshen commented on PR #3721:
URL: https://github.com/apache/bookkeeper/pull/3721#issuecomment-1408594064

   @horizonzy Nice catch!
   
   I have a question, if the user has a 30-node bookie cluster, 20 of which are rackA, and the other 10 are rackB, and the user has not enabled minNumRacksPerWriteQuorum and enforceMinNumRacksPerWriteQuorum;
   
   Now the user upgrades the pulsar cluster, the modification brought by this PR will be enabled,
   Will it happen that the data between the two racks is basically evenly distributed, resulting in double the traffic and storage pressure of rackB with only 10 nodes?
   
   In the random selection process of the old version, in theory, the traffic carried by rackA should be twice that of rackB.
   
   Do we need to pay attention to this?


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