Sometimes missing redis events? about redis-oplog HOT 2 CLOSED

For such use-case you should use a queue. Redis is fire and forget. I recommend RabbitMQ for such a scenario.

from redis-oplog.

A problem we encountered under higher load is that a subscription on a collection might finish after the document changes. So in client code you might first subscribe, then call a method that changes this collection, and then wait for changes on the collection. Waiting for changes might take forever because the method that changes the collection might finish before the subscription has finished. An event will be send to the redis server informing the change on the collection, but this event will be missed because there is no subscription yet. I fixed this by doing the subscription synchronously and not deferring it to a queue, see Caught-GmbH@588aea5

from redis-oplog.