Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how to persist mq data #376

Open
har2103 opened this issue Nov 15, 2019 · 2 comments
Open

how to persist mq data #376

har2103 opened this issue Nov 15, 2019 · 2 comments

Comments

@har2103
Copy link

har2103 commented Nov 15, 2019

hi team,

we are migrating to openshift and using gluster fs to mount mq data. we are mounting /mnt/mqm-data and /mnt/mqm-log in glusterfs. we see the qmgr data is getting persist along with log. but when we send some messages in queue after it restart the pod all messages are getting lost.

Need more info how we can persist mq data in persistent volume.

@arthurbarr
Copy link
Contributor

Can you confirm that you are using persistent messages? For example, a common issue we see is people using utilities like amqsput for testing, which don't set persistent messages by default (you can set the default persistence value for messages on the queue itself).

Otherwise, we would need to see more information about how you've set up your Persistent Volumes.

Please note that we have tested Gluster V3, V4 and V5, and they all have issues which make it an unsupported filesystem for MQ. See Testing statement. Note however, that this is due to a locking limitation, and is not the problem you are seeing here.

@har2103
Copy link
Author

har2103 commented Nov 19, 2019

Hi,

I was trying to test with amqsput which was not persisting in pvc. I tested with application then i was able to see. but for some queue we observed its still not persisting which is very weird behavior, Also another observation when we make queue property Defpersist to true the processing is happening very slow. MQ is picking messages very slow.

Please let me know what all pvc info you need?

mirskifa pushed a commit that referenced this issue Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants