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

Requeue in progress jobs and clean stale lock info on stop #1

Merged
merged 2 commits into from
Mar 9, 2021

Commits on Mar 5, 2021

  1. Requeue in progress jobs and clean stale lock info on stop

    In case there is a failover with a Redis Sentinel cluster with data loss
    there can be stale lock information which can cause job processing to be
    stuck if the max concurrency limit is reached. Therefore, re-enqueue the
    jobs which were in progress and also clean the stale lock info for the
    worker pool.
    
    For the cleanup to be thorough, the stop would need to be called on each
    worker pool instance.
    Kavish Gambhir authored and sudo-suhas committed Mar 5, 2021
    Configuration menu
    Copy the full SHA
    31eeb2d View commit details
    Browse the repository at this point in the history

Commits on Mar 8, 2021

  1. Configuration menu
    Copy the full SHA
    1d9521b View commit details
    Browse the repository at this point in the history