mochengqian opened a new issue, #942: URL: https://github.com/apache/dubbo-go-pixiu/issues/942
PR #932 rebuilds the consistent hash view from the healthy endpoint set during snapshot publication and lazy access. Maglev and ring-hash paths can still pay unnecessary rebuild cost when runtime health or membership updates publish a successor snapshot whose healthy set is effectively unchanged. Proposed: - Track enough snapshot identity to reuse the previous consistent hash when the healthy endpoint set and hash config are unchanged. - Extend benchmarks to cover health flaps and membership churn for ring-hash and Maglev clusters. - Keep correctness first: never reuse a hash across endpoint identity, address, or hash config changes. Reference: listed as a known follow-up in PR #932. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
