From 92c8408fba957a8ded13f7e285da290502735234 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Fri, 20 Aug 2010 14:54:03 +1000 Subject: [PATCH] Dont set next_interval to 0. This can cause ctdbd to spin at 100% in the eventsystem, creating a timed event that will immediately trigger again and again. On uniprocessors this cause the eventscript we are actually waiting for to basically become cpu starved and never complete. --- server/ctdb_monitor.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/ctdb_monitor.c b/server/ctdb_monitor.c index 5cc46089..7f5da5c3 100644 --- a/server/ctdb_monitor.c +++ b/server/ctdb_monitor.c @@ -203,7 +203,7 @@ static void ctdb_startup_callback(struct ctdb_context *ctdb, int status, void *p } else if (status == 0) { DEBUG(DEBUG_NOTICE,("startup event OK - enabling monitoring\n")); ctdb->done_startup = true; - ctdb->monitor->next_interval = 0; + ctdb->monitor->next_interval = 2; ctdb_run_notification_script(ctdb, "startup"); } -- 2.34.1