You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@helix.apache.org by GitBox <gi...@apache.org> on 2020/11/10 19:22:17 UTC

[GitHub] [helix] pkuwm opened a new issue #1524: Enable Dynamic Routing Cache Update for SharedZkClient and DedicatedZkClient

pkuwm opened a new issue #1524:
URL: https://github.com/apache/helix/issues/1524


   Dynamic routing cache update is only supported for `FederatedZkClient`. We've seen an issue that if a sharding key is added after a SharedZkClient is created, the sharding key will not be found in the routing cache of the SharedZkClient, until a new SharedZkClient is created which will read all sharding keys from metastore.
   
   This issue tracks the work of enabling dynamic routing update for SharedZkClient and DedicatedZkClient.


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



---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For additional commands, e-mail: reviews-help@helix.apache.org