We recently switched out redis for keydb on our web app at my company. We’ve got 2 instances up that are configured in the active replication mode. Since the changeover, we’ve noticed duplicate jobs being created and some jobs never being queued up. We’re receiving no errors on enqueuing the jobs, they just fail to persist in the keydb db.
We’ve run several experiments with a simple script that just enqueues jobs at a fast rate and then processes them.
- all writes going to one instance, all reads from one instance, no issues
- writes going to both instances, all reads from one instance, no issues
- writes going to both instances, reads from both instances, duplicates and dropped jobs
Is there something we can look into to see why the db may be duplicating and dropping jobs?