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
We are trying to add a mechanism where we produce msgs at 5-6 qps but we want to consume those msgs after 3 hours of delay since produce.
We consume in a batch of 90 messages. Each msg of ~150 bytes.
In the first batch, we checked the timestamp and add delay of 3 hrs - (Date.now()- msg_produce_timestamp) i.e slept for ~3 hours.
We are using manual commit (autoCommit: false).
Now the issue with this workflow is, after waking up from sleep, the consumer is picking all 90 msgs from partition:0 only.
As a result, lag keeps increasing in the other 9 partitions.
Is there any way/configuration to optimize this flow so that we could consume from each partition equally and hence the lag will be the same in all partitions?
The text was updated successfully, but these errors were encountered:
Environment Information
Topic: profile_updates
Partitions: 10
We are trying to add a mechanism where we produce msgs at 5-6 qps but we want to consume those msgs after 3 hours of delay since produce.
We consume in a batch of 90 messages. Each msg of ~150 bytes.
In the first batch, we checked the timestamp and add delay of
3 hrs - (Date.now()- msg_produce_timestamp)
i.e slept for ~3 hours.We are using manual commit (autoCommit: false).
Now the issue with this workflow is, after waking up from sleep, the consumer is picking all 90 msgs from partition:0 only.
As a result, lag keeps increasing in the other 9 partitions.
Is there any way/configuration to optimize this flow so that we could consume from each partition equally and hence the lag will be the same in all partitions?
The text was updated successfully, but these errors were encountered: