You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/07/28 04:13:17 UTC

[GitHub] [pulsar] Jason918 commented on pull request #16563: [improve][broker]improve the getAntiAffinityNamespaceOwnedBrokers check exclude the current namespace cause count add.

Jason918 commented on PR #16563:
URL: https://github.com/apache/pulsar/pull/16563#issuecomment-1197636328

   > there is some case
   > `broker-0` own `ns-0 bundle-0`;
   > `broker-1` own `ns-1 bundle-0`;
   > `broker-2 `own `ns-2 bundle-0`;
   > then another ` ns-2 bundle-1` need choice a broker to load. As the old policy, `broker-0 broker-1 and broker-2` are all satisfy the least NamespaceCount; but if `ns-2 bundle-1` load to `broker-0 or broker-1 `will broke the anti affinity balance. `ns-2 bundle-1` need be load by broker-2 is better.
   
   What's the anti affinity setting in this case?


-- 
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@pulsar.apache.org

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