Hi @pjaikumar,
several other users who have run into this were using G1GC. Is that also the case for your cluster?
If so, the following change is important:
It is worthwhile double checking that the G1 settings are correct compared to that PR, i.e., that you have:
-XX:G1ReservePercent=25
-XX:InitiatingHeapOccupancyPercent=30
in your jvm.options file.
If you are not using G1 or you are using G1 with above settings, I would be interested in seeing your GC logs from Elasticsearch (together with exception info from log file) if this should reoccur.