Commit graph

6 commits

Author SHA1 Message Date
David Turner
e5fd63bbb8
More detail around packet captures (#111835)
Clarify that it's best to analyse the captures alongside the node logs,
and spell out in a bit more detail how to use packet captures and logs
to pin down the cause of a `disconnected` node.
2024-08-13 21:55:38 +01:00
David Turner
42e5293c04
Capture GC logs alongside heap dumps (#109087)
GC logs can be important to understand a heap dump, especially if
there's lots of unreachable objects and the GC is struggling to keep up.
2024-05-28 04:54:04 -04:00
David Turner
92eae448e9
Clarify that we need stack dumps of the main process (#103391)
ES comprises more than one Java process, but it's the main one which
matters when looking at stack dumps.
2023-12-13 08:41:30 -05:00
David Turner
5dff56a00e
Mention network handler logging in docs (#100118)
Mentions the `InboundHandler` (and `OutboundHandler`) as potential
sources of useful log messages when tracking down a network threading
bug.
2023-10-02 08:52:16 +01:00
David Turner
bf34036c8c
Discovery troubleshooting next steps (#99743)
Adds a little more detail on how to react if you see evidence that the
Elasticsearch process is pausing for a long time due to long GCs or VM
pauses.
2023-09-21 13:00:13 +01:00
David Turner
09e53f9ad9
Enhance docs around network troubleshooting (#97305)
Discovery, like cluster membership, can also be affected by network-like
issues (e.g. GC/VM pauses, dropped packets and blocked threads) so this
commit duplicates the troubleshooting info across both places.
2023-07-10 10:57:44 +01:00