This message was deleted.
# troubleshooting
s
This message was deleted.
b
I haven't seen this being set. What I've seen normally done is to reduce heap size or direct memory settings.
s
@Ben Krug Okay... will try that
b
Let us know how it goes!
s
@Ben Krug It is not working
now we are seeing this error in historical
Copy code
961.954: [Full GC (Allocation Failure) 961.954: [CMS965.859: [CMS-concurrent-mark: 6.859/6.866 secs] [Times: user=19.09 sys=0.41, real=6.87 secs]


1000.342: [GC (GCLocker Initiated GC) 1000.342: [ParNew: 460095K->460095K(460096K), 0.0000383 secs] 8337535K->8337535K(8337536K), 0.0001727 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
GC locker: Trying a full collection because scavenge failed
1000.342: [Full GC (GCLocker Initiated GC) 1000.342: [CMS1006.562: [CMS-concurrent-mark: 6.929/6.938 secs] [Times: user=16.74 sys=0.26, real=6.94 secs]
@Ben Krug
g
note that in Druid 25 (the latest release) you can start druid via the
bin/start-druid
script, and it will automatically determine reasonable configs given the available resources on the server
I would try this first and see if it solves your problem
if it doesn't then let us know 🙂