GitHub user git-hulk added a comment to the discussion: Adding Empty shard causing mass timeouts when under heavy load
Hi @bseto > It's January now, and the load is similar (but slightly lower than it was in > November/December), but when I tried migrations on the 2nd and 3rd largest > clusters after setting persist-cluster-nodes-enabled no, it seems those > clusters no longer have issues. This shouldn't be an issue because it only writes the cluster nodes information into the local file nodes.conf. > I'm also noticing it's not every node. It's usually maybe 10% of the nodes in > the cluster that get hammered hard and have clients continuously > connect/disconnect. Could you please provide the logs of the cluster node? It might have the potential clues about what's going on at that time. For example, whether this node role was changed or not? > Is there a way I can confirm if SetClusterNodes is indeed taking too long and > the culprit? You could see the command_stats via the `info` command. GitHub link: https://github.com/apache/kvrocks/discussions/3331#discussioncomment-15430837 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
