Anyway to reserve gc.log? mine is always refresh after dremio restarted

Hi there,

Is there any option helps to reserve the gc.log? mine is refresh after dremio is restarted, so it’s hard to figure out why the service is stopped


@quangth2 - If you are using our Helm charts, please try adding a path on the persistent volume to values.yaml where the logs can be written to extraStartParams:

extraStartParams: >-


It’s already in my config
Have added -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=50m
Let’s see how it works

@quangth2 Is /opt/dremio/data/logs a PVC?

Hi @balaji.ramaswamy,
Yes, indeed. I pull all the log directory into the PVC
All the other logs are still persistent. Only gc log is refreshed after server restart

@quangth2 Does it happen even after adding the below?

 -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=50m

@balaji.ramaswamy it still happens

But good news is because it’s written in new file name after service restarted, so the old file still be kept


@quangth2 That looks like it is working as expected

Hi there,
Found it article and it could be helpful

Using ‘%t’ parameter is much easier to keep the log file, since every time the service startup, it will write gc log to different file. Just be aware to clean your logs often, because it will be kept forever