Operation: ( remove ) failed on key: [(a shard in) DECISION ] about dyno-queues

[apanicker-nflx]

What version of Conductor are you using?
Based on the error message, this seems like an error thrown by the queuing layer (DynoQueues or Redis, maybe). I would recommend you to check your redis configurations.

[SuperMasterBlasterLaser]

@apanicker-nflx I'm using this Docker Compose settings. I know that Dynomite is using redis are there any settings to add to this compose file?

[apanicker-nflx]

@smukil Can you help with deciphering this dyno queue error. Thanks

[manan164]

@apanicker-nflx Even we are facing this issue. I have earlier raised this ticket. Because of this issue, the queue size of HTTP and deciderQueue will eventually become very large and we have to delete it manually.

[smukil]

The above errors could likely be due to a failure in achieving quorum or the dynomite server node(s) are unreachable temporarily (you would see other related errors in the logs if this is the case).

If you have no other information in the logs, the best way to figure out the actual error would be to attach a debugger to your java process and add breakpoints in remove() and step in to see what's going on.

Also, please see the updated README for the project status.

[manan164]

Hi @smukil , I see that if we revert the commit then it is working fine. But commit says it fixes the removal part. I see that every time removed is 0 so it won't take if condiction path and a message from the queue will not get removed and it just gets piled up.