This message was deleted.

OOM Killer killed it. The memory usage configuration is not correct.

@Didip Kerabat I had given these parameters as per druid recomendation only

value: -server -Xms8G -Xmx8G -XX:MaxDirectMemorySize=12G -Duser.timezone=UTC
            -Dfile.encoding=UTF-8 -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager
            -XX:+UseConcMarkSweepGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Djute.maxbuffer=16777216

resources:
          limits:
            cpu: "10"
            memory: 100Gi

# Processing threads and buffers
    druid.processing.buffer.sizeBytes=500000000
    druid.processing.numMergeBuffers=3
    druid.processing.numThreads=9
    druid.processing.tmpDir=var/druid/processing

@sridhara , have you defined

requests

memory?, as said @Didip Kerabat, 137 exit code is an OOM killer from system to the process caused by high memory request

if you update to Druid 25, there’s a script that auto tunes memory configs for you

Issue got resolved... Actually issue is not with memory... issue is with cores