-
Story
-
Resolution: Done
-
Undefined
-
None
It's difficult to persist some troubleshooting or audit artifacts to a persistent store. In particular, with a GC log configuration:
- name: JAVA_ARGS_APPEND value: >- -Xlog:gc*,gc+age=trace,gc+heap=debug,gc+promotion=trace,safepoint:file=/opt/artemis-broker/data/gc.log::filecount=10,filesize=10M
The init container is unable to complete:
[0.001s][error][logging] Error opening log file '/opt/artemis-broker/data/gc.log': No such file or directory
Suggest a configuration for a user-defined volume that can persist these types of artifacts.
UPDATE: JAVA_OPTS instead of JAVA_ARGS_APPEND does allow this configuration to work. That said, still might be good to have a separate volume for these types of artifacts to keep them separate from the default artemis data store.
- depends on
-
ENTMQBR-7434 The AMQ operator should support an option of mounting multiple volumes
- Closed