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

PubSub: messages with group topics are sent many times per node #27421

Open
yufei-cai opened this issue Jul 26, 2019 · 3 comments
Open

PubSub: messages with group topics are sent many times per node #27421

yufei-cai opened this issue Jul 26, 2019 · 3 comments
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted nice-to-have (low-prio) Tasks which make sense, however are not very high priority, feel free to help out!

Comments

@yufei-cai
Copy link
Contributor

Setup:

  • 100 actors in actor system A subscribe to 1 topic with groups distinct from one another.
  • 1 message is published in actor system B on the topic with sendOneMessageToEachGroup=true.

Expected behavior:
1 message is sent from B to A, where it gets broadcasted to the 100 subscribers.

Actual behavior:
100 messages are sent from B to A.

The actual behavior is a logical conclusion of the documentation (assuming "topic"==="topic identifier": "the message is sent over the wire only once per node (that has a matching topic)" and "the group id is used it is part of the topic identifier", desto the optimization does not apply for message published to multiple groups). Is the actual behavior reasonable? Does the documentation leaves the right impression? I believed the "expected behavior" for years...

@patriknw
Copy link
Member

It’s supposed to send the once over the wire so your understanding of expected behavior is correct. Not sure if the ”group” aspect changes any of that. Have to look into the details, but on vacation now.

@patriknw
Copy link
Member

It looks like when using groups that optimization is not used. I don't know how difficult it would be to improve this, and it's not something we can work on right now. I hope you can solve it by using ordinary topics.

@patriknw patriknw added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted nice-to-have (low-prio) Tasks which make sense, however are not very high priority, feel free to help out! labels Aug 13, 2019
@yufei-cai
Copy link
Contributor Author

Yes, the optimization works without topic group. Some warning in the documentation would be nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted nice-to-have (low-prio) Tasks which make sense, however are not very high priority, feel free to help out!
Projects
None yet
Development

No branches or pull requests

2 participants