You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@helix.apache.org by GitBox <gi...@apache.org> on 2019/07/15 22:32:50 UTC

[GitHub] [helix] i3wangyi opened a new issue #332: Issue when client ONLY sets cluster level ANY throttle config

i3wangyi opened a new issue #332: Issue when client ONLY sets cluster level ANY throttle config
URL: https://github.com/apache/helix/issues/332
 
 
   The current implementation has a loophole when 
   1. When client **ONLY** sets cluster level ANY throttle config (no specific type throttle)
   2. The config won't be respected when charging load_rebalance or recovery_rebalance types
   
   The root cause is the implementation relies on the counters in the hashmap, where each type including ANY is of different entry.

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


With regards,
Apache Git Services