-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
The main question: how should be persistence configured with AMQ 7 image?
Previously we in AMQ 6.x, there's was an template that adds volumeMount pointing to /opt/amq/data.
I've tried to replicate the same configuration on AMQ 7 image. However, there's a kink of two.
On AMQ 7 artemis create isn't very happy about writting into $HOME once there's already mounted volume on /home/jboss/broker/data.
Notice that /data as PV are set with write-all perms but different user, group combination.
sh-4.2$ ls -l /home/jboss/ total 0 drwxr-xr-x. 9 1000200000 root 85 May 17 12:20 broker sh-4.2$ ls -l /opt/amq/ total 44 -rw-rw-r--. 1 jboss root 22122 Feb 1 04:24 LICENSE -rw-rw-r--. 1 jboss root 179 Feb 1 04:24 NOTICE -rw-rw-r--. 1 jboss root 5391 Feb 1 04:24 README.html drwxrwxr-x. 4 jboss root 206 Apr 23 20:05 bin drwxrwxr-x. 2 jboss root 6 Apr 23 20:04 conf drwxrwxrwx. 6 65534 65534 4096 May 17 10:30 data drwxrwxr-x. 3 jboss root 22 Apr 18 22:27 docs drwxrwxr-x. 3 jboss root 17 Apr 18 22:27 etc drwxrwxr-x. 6 jboss root 80 Apr 18 22:27 examples drwxrwxr-x. 3 jboss root 4096 Apr 18 22:27 lib drwxrwxr-x. 2 jboss root 88 Feb 1 04:46 schema drwxrwxr-x. 10 jboss root 253 Apr 18 22:27 web
+ echo 'Creating Broker with args --user user --password password --role admin --name broker --allow-anonymous --http-host 10.131.1.233 --host 0.0.0.0 ' Creating Broker with args --user user --password password --role admin --name broker --allow-anonymous --http-host 10.131.1.233 --host 0.0.0.0 + /opt/amq/bin/artemis create /home/jboss/broker --user user --password password --role admin --name broker --allow-anonymous --http-host 10.131.1.233 --host 0.0.0.0 --java-options '-XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MaxMetaspaceSize=100m -XX:+ExitOnOutOfMemoryError' The path '/home/jboss/broker' is not writable.
I was able to workaround default behaviour by adding mount to /opt/amq/data and adding env var $AMQ_EXTRA_ARGS="--data /opt/amq/data". That seems to work fine.
Any plans how persistence config is going to be addressed?
- clones
-
ENTMQBR-1655 [AMQ7] how to enable message persistence with PV
-
- Closed
-