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

Explicitly state which RabbitMQ versions are supported #48

Closed
johanrhodin opened this issue Jan 21, 2020 · 3 comments
Closed

Explicitly state which RabbitMQ versions are supported #48

johanrhodin opened this issue Jan 21, 2020 · 3 comments

Comments

@johanrhodin
Copy link
Contributor

It seems like RabbitMQ 3.7.16 can't use 0.4.3 reliably. It would be good to see that in an overview. (The issue was that all queues displayed as NaN.)

@noxdafox
Copy link
Owner

Hello,

the goal would be to support all versions from v3.7.x onwards but the things got a little bit complicated. RMQ slightly changed one of the behaviours which the queue deduplication relies upon. My initial plan was to maintain two separated releases for v3.7.x and v3.8.x. Nevertheless the change was introduced in v3.7.18 which was a "transition release".

Moreover, the behaviour mentioned above used to be in rabbitmq-common, it has been moved within rabbitmq-server internals. This makes me wonder whether RMQ devs are intending to remove that behaviour in the long run as they are planning to refactor the queues support in the upcoming versions. As I mentioned in #37 I am planning to reach out the devs community to ask what are the plans on the long run so I can adopt the plugin accordingly but right now I am a bit short of free time.

I will try to spin up a v3.7.16 cluster and see if I can reproduce the issue and fix it asap.

@noxdafox
Copy link
Owner

noxdafox commented Jan 30, 2020

To answer your question: v0.4.3 minimum supported RMQ version is v3.7.17.

Version below v3.7.17 shall use the plugin v0.4.2. The only difference across the two versions is the support for new RMQ > v3.7.17.

I will update the README accordingly.

noxdafox added a commit that referenced this issue Jan 30, 2020
@noxdafox
Copy link
Owner

Readme updated. Please reopen this issue if is yet not clear or you encounter other issues related to version support.

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