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 2021/05/21 10:01:34 UTC

[GitHub] [pulsar] frankjkelly edited a comment on issue #10627: Documentation: Suggest adding documentation for supported bundle split algorithms

frankjkelly edited a comment on issue #10627:
URL: https://github.com/apache/pulsar/issues/10627#issuecomment-845835933


   Thanks @Anonymitaet exactly - it gets pretty interesting to understand how all those parameters will interact.
   I'm particularly interested in how each algorithm behaves when we add brokers (we're hoping to implement Kubernetes autoscaling)- how quickly would those brokers be discovered and how  quickly some load would be redirected to those new brokers.
   
   In my limited experience with `range_equally_divide` it's not until we hit the `loadBalancerBrokerOverloadedThresholdPercentage` and the broker is overloaded that some namespace bundles will be split and offloaded but at that point usually the load on the broker is pretty high so that the offload seems to be "expensive" or at least take a long time and then our Pulsar Clients start timing out (we have them set with a 3 second timeout due to the near-real-time nature of our use-cases).
   
   For us we'd rather have a way that was a faster balancing (but perhaps less precisely load balanced) than one that was more accurately load balanced but takes longer to shed load. Again we're pretty new to this but would appreciate to hear perspectives or pointers to code. Thanks!


-- 
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:
users@infra.apache.org