I have learned that
front-end service needs to calculate which node the execution belongs to according to
hash32(executionID) MOD shardCount MOD NodeCount
shardContext contains a lot of runtime data in memory to speed up the read/write of the server.
So my question is when the history service nodes are updated, the number of nodes changes during the process. This will change the assignment of a shard to a different Node, and the memory data needs reconstruction. Will this greatly affect the performance of history service?
I am not sure if my concern is a valid one. And very willing to have different opinions on this quesition.