Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Pub/Sub message stuck for specific ordering_key (user_id)

Hi, my workplace has been using pub/sub as messenger in our system.
We use user_id as the ordering key, and this week our system faced problem where messages from one specific user (which also is the ordering key), are always successfully published but subscriber/listener does not receive it at all. Other messages from different user does not get this problem.

This happens for all message of the one specific user/ordering_key for several days until we finally restarted our listener/subscriber, only then it finally works normally again.

I'm having assumption that there's something wrong with the subscriber ordering mechanism on the specific ordering key at one point, causing the newer message could not be received.

Does anyone ever face this kind of problem?
And how do I prevent this from happening in the future?

0 1 185
1 REPLY 1