532ade7816
Today the lag detector may remove nodes from the cluster if they fail to apply a cluster state within a reasonable timeframe, but it is rather unclear from the default logging that this has occurred and there is very little extra information beyond the fact that the removed node was lagging. Moreover the only forewarning that the lag detector might be invoked is a message indicating that cluster state publication took unreasonably long, which does not contain enough information to investigate the problem further. This commit adds a good deal more detail to make the issues of slow nodes more prominent: - after 10 seconds (by default) we log an INFO message indicating that a publication is still waiting for responses from some nodes, including the identities of the problematic nodes. - when the publication times out after 30 seconds (by default) we log a WARN message identifying the nodes that are still pending. - the lag detector logs a more detailed warning when a fatally-lagging node is detected. - if applying a cluster state takes too long then the cluster applier service logs a breakdown of all the tasks it ran as part of that process. |
||
|---|---|---|
| .. | ||
| adding-removing-nodes.asciidoc | ||
| bootstrapping.asciidoc | ||
| discovery-settings.asciidoc | ||
| discovery.asciidoc | ||
| fault-detection.asciidoc | ||
| publishing.asciidoc | ||
| quorums.asciidoc | ||
| voting.asciidoc | ||