Skip to content

Conversation

@d-j-hatton
Copy link
Contributor

Use the Zocalo site configuration throughout to remove the need for Diamond specific information. A new storage plugin will need to be added to the configuration to hold zocalo.dlq.purge_location where purged messages will be dumped.

I think that all environments should work with the exception of a RabbitMQ test environment for dlq_check as it makes use of the RabbitMQ management API and the relevant credentials.

Also add dlq_check for RabbitMQ to IT health checks.

…flag is set. Makes use of the rabbitmq management API
@d-j-hatton d-j-hatton requested a review from Anthchirp October 1, 2021 11:19
@d-j-hatton d-j-hatton mentioned this pull request Oct 1, 2021
8 tasks
Co-authored-by: Markus Gerstel <2102431+Anthchirp@users.noreply.github.com>
Co-authored-by: Markus Gerstel <2102431+Anthchirp@users.noreply.github.com>
d-j-hatton and others added 9 commits October 4, 2021 09:12
Co-authored-by: Richard Gildea <rjgildea@users.noreply.github.com>
Co-authored-by: Richard Gildea <rjgildea@users.noreply.github.com>
Co-authored-by: Richard Gildea <rjgildea@users.noreply.github.com>
Co-authored-by: Richard Gildea <rjgildea@users.noreply.github.com>
@d-j-hatton
Copy link
Contributor Author

I've tested these on the RabbitMQ live server and they work except that the ack in dlq_purge crashes complaining with pika.exceptions.ChannelClosedByBroker: (406, 'PRECONDITION_FAILED - unknown delivery tag 1') so either there's a mix up with what the delivery tag should be here or something is going wrong in workflows.

I am nacking the messages directly from http://rabbitmq1.diamond.ac.uk:15672/#/queues/zocalo/transient.destination for testing. Don't know if that causes problems

@d-j-hatton d-j-hatton merged commit 6c10901 into master Oct 11, 2021
@d-j-hatton d-j-hatton deleted the rabbitmq-dlq branch October 11, 2021 08:39
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

Successfully merging this pull request may close these issues.

4 participants