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

Administrator should be able to clear 'cooldown' request state #524

Closed
stevenschlansker opened this issue Apr 16, 2015 · 3 comments
Closed
Assignees

Comments

@stevenschlansker
Copy link
Contributor

Often cooldown happens because of an administrative error. Perhaps a required database is down, or there was a temporary DNS outage.

Once the administrator believes she has cleared the outage, it is frustrating to watch Singularity cool your (hypothetically now working) task off. Especially if you are getting phone calls from frustrated end users.

A button to reset the cooldown state (or at least override it once, making the delayed tasks launch immediately) would be very helpful.

@tpetr
Copy link
Contributor

tpetr commented May 19, 2015

We've been burned by this internally too -- we're going to fix it in 2 ways: a button to clear the cooldown state of the request, and fix Run Now to work on scheduled tasks (only supported for cron jobs currently)

@tpetr
Copy link
Contributor

tpetr commented Jul 1, 2015

^ added Exit Cooldown button to Request page when request is in cooldown state, which clears the cooldown setting and immediately schedules all pending tasks

@tpetr tpetr closed this as completed Jul 1, 2015
@benhardy
Copy link
Contributor

benhardy commented Jul 1, 2015

Thanks @tpetr !

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

3 participants