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

Bugfix: federation queue link, dont transfer messages unless consumer exists #637

Merged
merged 18 commits into from
May 21, 2024

Conversation

viktorerlingsson
Copy link
Member

@viktorerlingsson viktorerlingsson commented Feb 28, 2024

WHAT is this pull request doing?

Stops federation queue links from transferring messages unless there is an active consumer on the downstream.
federate now publishes directly to vhost instead of using a client. This allows us to use the immediate flag to make sure we don't federate messages unless there is a consumer on the downstream queue.

HOW can this pull request be tested?

Run the specs

@viktorerlingsson viktorerlingsson force-pushed the bugfix_federation_dont_transfer_unless_consumer branch from 0d9e1e4 to 8421880 Compare March 27, 2024 13:03
@CLAassistant

This comment was marked as resolved.

@viktorerlingsson viktorerlingsson force-pushed the bugfix_federation_dont_transfer_unless_consumer branch from 927945b to 84ae73e Compare April 2, 2024 13:28
@viktorerlingsson viktorerlingsson force-pushed the bugfix_federation_dont_transfer_unless_consumer branch from fb24e65 to 335c1c6 Compare April 10, 2024 08:38
@viktorerlingsson viktorerlingsson marked this pull request as ready for review April 10, 2024 09:01
@viktorerlingsson viktorerlingsson requested review from kickster97, carlhoerberg and spuun and removed request for kickster97 and carlhoerberg April 10, 2024 09:02
@spuun
Copy link
Member

spuun commented Apr 17, 2024

Just a little remark that came to my mind:

By removing the local connection and channel it may be harder to understand where messages comes from. Dunno how big of a deal it is, but just want to mention it.

If I can manage to break out Client, Connection, Channel and Consumer (which I'd like to do) it would be possible to make these entities without actually having a real TCP connection.

@viktorerlingsson viktorerlingsson force-pushed the bugfix_federation_dont_transfer_unless_consumer branch from dfe2646 to 18f25bd Compare May 20, 2024 13:53
@viktorerlingsson viktorerlingsson requested a review from snichme as a code owner May 20, 2024 13:53
@viktorerlingsson viktorerlingsson merged commit 9b31337 into main May 21, 2024
25 of 27 checks passed
@viktorerlingsson viktorerlingsson deleted the bugfix_federation_dont_transfer_unless_consumer branch May 21, 2024 09:13
@kickster97
Copy link
Member

If I can manage to break out Client, Connection, Channel and Consumer (which I'd like to do) it would be possible to make these entities without actually having a real TCP connection.

@spuun, We should remember this now that we have the PR for the abstraction out :)

viktorerlingsson added a commit that referenced this pull request Sep 20, 2024
… exists (#637)

Stops federation queue links from transferring messages unless there is an active consumer on the downstream.
federate now publishes directly to vhost instead of using a client. This allows us to use the immediate flag to make sure we don't federate messages unless there is a consumer on the downstream queue.
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.

Federated queues shouldn't transfer msgs unless downstream has consumers
4 participants