This message was deleted.
# troubleshooting
s
This message was deleted.
i
is there enough memory for 24 gb heap? How much memory is available per node?
j
I think around 15GB, but I thought it would not get the 24g but whatever we have in
druid_processing_buffer_sizeBytes
by
druid_processing_numThreads
, I currently have 12 and 4 respectively which comes down to less than 15GB
i
This looks like the issue, I would make those much smaller as it is more than each node can allocate
Copy code
config: {
        DRUID_XMX: '24g',
        DRUID_XMS: '24g',
d
This does not look right.
Copy code
[
{"path"\:"/opt/druid/var/druid/segment-cache","maxSize"\:"1754200000000"}, {"path"\:"/opt/druid/var/druid/segment-cache","maxSize"\:"1858900000000"}, {"path"\:"/opt/druid/var/druid/segment-cache","maxSize"\:"1858900000000"}, {"path"\:"/opt/druid/var/druid/segment-cache","maxSize"\:"1858900000000"}
]
They are all pointing at the same path.
j
Shouldn't they be one entry in the array per replica? It's true there are 12 replicas and only 4 entries in the array
Each entry is a path to each replica
O should really be one entry in the array?
mm I am wrong here, should really be different paths yeah
g
if the historical logs just end, without it starting up successfully, for clues you can check dmesg (to see if it was oom-killed) or historical.stdout.log (for messages from jvm)
typically the reason is out of memory-- if it's configured to use more memory than you have available on the system, or more off heap memory than the jvm direct memory limit