Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For replicate command, live mode - how do we handle data-consistency in riot? #130

Open
raghu-nandan-bs opened this issue Aug 21, 2023 · 0 comments

Comments

@raghu-nandan-bs
Copy link

When we are replicating data from one redis database to another using live mode, two separate jobs run in parallel - snaptshot job and live only job. Each job has its own queue where items that are read are stored before it is drained by itemWriters in the job.

Lets say the queue size in snapshot job is reasonably large. An item with key 'x' is read and stored in the queue.
Meanwhile, the key was updated, causing the live job to read the key and write it to the destination, all the while the key's item is still waiting in the snapshot job's queue.

The item is then picked by writer in snapshot job and replace existing key in destination redis. Will this not cause inconsistency?

live-job

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant