You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug:NATS PullSubscriber works not clear with max_workers > 1 #2563
Describe the bug
Max_workers with value > 1 consumes more messages than value. The correct number of messages is processed at the same time, but the part that exceeds max_workers is recognized by NATS as being sent to the client and then redelivered, resulting in duplicate messages
I think we should try to find a workaround to move the lock to reading phase instead of processing.
Also looks related to #2531
I think this is a bug in the core functionality. Do you have an estimated timeline for a fix?
On a separate note, I've also observed a similar issue with Redis Stream, where tasks are canceled before they can finish processing a message during shutdown, similar to what's described in #2462.
@szkytk I am not sure about timeline - I am busy a lot of AG now and also have a bugs with higher priority. But, I hope to fix the problem right after the hottest things fix.
Activity
Lancetnik commentedon Oct 9, 2025
I think we should try to find a workaround to move the lock to reading phase instead of processing.
Also looks related to #2531
szkytk commentedon Oct 14, 2025
@Lancetnik
I think this is a bug in the core functionality. Do you have an estimated timeline for a fix?
On a separate note, I've also observed a similar issue with Redis Stream, where tasks are canceled before they can finish processing a message during shutdown, similar to what's described in #2462.
Lancetnik commentedon Oct 14, 2025
@szkytk I am not sure about timeline - I am busy a lot of AG now and also have a bugs with higher priority. But, I hope to fix the problem right after the hottest things fix.