Replies: 2 comments
-
@SheseR questions belong to discussions, not issues. I cannot comment on what happens in your system, you haven't provided a way to reproduce, no logs, no traffic capture, effectively nothing for the maintainers to work with. What I can confirm is that
If you need to process messages strictly in batches, I'd say you should consider using RabbitMQ streams but I am not aware of the state of Ruby clients for that protocol. And then you'd have to give up on using Kicks, too. But it will allow you to consume in batches, and repeatedly if necessary, more predictably than with a queue and a channel prefetch. |
Beta Was this translation helpful? Give feedback.
-
Per my understanding, this is not supported by Kick directly, but I have some code extension to Sneakers somewhere I can probably share to achieve exactly this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey all!
The my idea is to collect 10 messages, and handle those ones in the single process, so I do that like
The worker waits for 10 messages before handling. it is work fine, but if there is no 10 messages in the worker during some time, the server close channel, and worker downs at all
So I wanna to set some 'idle timeout' and catch it on this worker for handling of existed messages.
Does sneakers support that ?
thanks a lot! -))
Beta Was this translation helpful? Give feedback.
All reactions