mirror of
https://github.com/samba-team/samba.git
synced 2025-03-08 04:58:40 +03:00
eventscript: don't make ourselves healthy if we're under ban_count
If we've timed out, but we've not timed out more than ctdb->tunable.script_ban_count, we pretend we haven't. There's a logic bug in the way this is done: if we were unhealthy before, this would set us to "healthy" again (status == 0). I don't think this would happen in real life, but it's a little surprising. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit e6488c0e05bab5c4c2c0a6370930b0b27e5ed56e)
This commit is contained in:
parent
928b8dcb31
commit
9914d3f561
@ -130,7 +130,7 @@ static void ctdb_health_callback(struct ctdb_context *ctdb, int status, void *p)
|
||||
DEBUG(DEBUG_ERR, ("Maximum timeout count %u reached for eventscript. Making node unhealthy\n", ctdb->tunable.script_ban_count));
|
||||
} else {
|
||||
/* We pretend this is OK. */
|
||||
status = 0;
|
||||
goto after_change_status;
|
||||
}
|
||||
}
|
||||
|
||||
@ -168,6 +168,7 @@ static void ctdb_health_callback(struct ctdb_context *ctdb, int status, void *p)
|
||||
|
||||
}
|
||||
|
||||
after_change_status:
|
||||
next_interval = ctdb->monitor->next_interval;
|
||||
|
||||
ctdb->monitor->next_interval *= 2;
|
||||
|
Loading…
x
Reference in New Issue
Block a user