-
Notifications
You must be signed in to change notification settings - Fork 224
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
Pub/Sub message ordering support #724
Conversation
5f50abb
to
2b40def
Compare
oh awesome. taking a look, back from kubecon |
Looks like you got tripped up on a data race in the unit test, could you take a look @skymeyer ? overall this code looks good, it might be a simple fix for just the test.
|
Thanks @n3wscott - will take a look, prob need to add some lock. |
Signed-off-by: Jelle Vink <jelle.vink@gmail.com>
2b40def
to
4d36d5b
Compare
@n3wscott I was setting |
I tested pubsub ordering key with this library but I found an issue. When you send 3 or more messages, with same ordering key, receiver only waits for first one, second and third messages are consumed concurrently. I added a 5 second sleep in message handler in order to check that the total amount of time was 15 seconds as expected, but it was 10 second. It can also be checked with logs. When I try the same directly invoking pubsub receiver, it worked as expected.
|
Question from @rriolobos is tracked under #753. |
Fixes #723
Message ordering may require producing the events using an explicit regional endpoint. Not sure if we should add a helper to produce a pubsub client using a regional service endpoint or leave this as an exercise to the integrator.