The Master Es Node is pegged at 100% CPU Utilization after adding some new logs for ingestion. Below is a sample of hot threads:
95.3% (476.2ms out of 500ms) cpu usage by thread 'elasticsearch[ip-xx-xx-xx-xxx][clusterService#updateTask][T#1]'
6/10 snapshots sharing following 33 elements
java.util.zip.Deflater.deflateBytes(Native Method)
java.util.zip.Deflater.deflate(Deflater.java:430)
java.util.zip.Deflater.deflate(Deflater.java:352)
java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:251)
java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:211)
java.io.BufferedOutputStream.write(BufferedOutputStream.java:122)
org.elasticsearch.common.io.stream.OutputStreamStreamOutput.writeBytes(OutputStreamStreamOutput.java:42)
org.elasticsearch.common.io.stream.StreamOutput.write(StreamOutput.java:299)
java.util.zip.CheckedOutputStream.write(CheckedOutputStream.java:73)
com.fasterxml.jackson.core.json.UTF8JsonGenerator._flushBuffer(UTF8JsonGenerator.java:2003)
com.fasterxml.jackson.core.json.UTF8JsonGenerator._writeStringSegments(UTF8JsonGenerator.java:1148)
com.fasterxml.jackson.core.json.UTF8JsonGenerator.writeFieldName(UTF8JsonGenerator.java:204)
Any ideas on why this might be happening?