new-slave.py should refuse to run if cluster is lagged
Bug #491748 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Won't Fix
|
High
|
Stuart Bishop |
Bug Description
If the cluster is lagged, there may be a problem. Even if there is not a problem, the script will block until lag is cleared. We should just abort if the cluster is lagged so the lag can be diagnosed and corrected.
Changed in launchpad-foundations: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Stuart Bishop (stub) |
milestone: | none → 3.1.12 |
Changed in launchpad-foundations: | |
milestone: | 3.1.12 → 10.01 |
Changed in launchpad-foundations: | |
milestone: | 10.01 → 10.03 |
To post a comment you must log in.
Also check for events to or from the new node_id in sl_event and sl_confirm (these might be laying around if the cleanup thread hasn't been run since a node with the same id has been dropped).