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

Make the reliability set more consistent with the reliability list #37

Open
linkyndy opened this issue Apr 6, 2019 · 0 comments
Open

Comments

@linkyndy
Copy link
Owner

linkyndy commented Apr 6, 2019

Because one cannot blocking-pop from a list and push to a sorted set, we first push to a list (reliably), then to the set. Because of this, jobs are not lost, but a job might not end up in the sorted set, which is actually the one used when rescheduling. Hence the job will never be rescheduled. This scenario is quite extreme, but there are chances it might happen.

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

No branches or pull requests

1 participant