summaryrefslogtreecommitdiffstats
path: root/ctdb/server/ctdb_monitor.c
diff options
context:
space:
mode:
authorRonnie Sahlberg <ronniesahlberg@gmail.com>2010-08-20 14:54:03 +1000
committerRonnie Sahlberg <ronniesahlberg@gmail.com>2010-08-20 15:00:45 +1000
commite040a966af084fddf451ac737f7af6bbf62a3a82 (patch)
tree28095655347b880cd95637509ecc28f9c9f8db78 /ctdb/server/ctdb_monitor.c
parent1ef66379d7c6771db09798824d242887080d6344 (diff)
downloadsamba-e040a966af084fddf451ac737f7af6bbf62a3a82.tar.gz
samba-e040a966af084fddf451ac737f7af6bbf62a3a82.tar.xz
samba-e040a966af084fddf451ac737f7af6bbf62a3a82.zip
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. (This used to be ctdb commit 92c8408fba957a8ded13f7e285da290502735234)
Diffstat (limited to 'ctdb/server/ctdb_monitor.c')
-rw-r--r--ctdb/server/ctdb_monitor.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/ctdb/server/ctdb_monitor.c b/ctdb/server/ctdb_monitor.c
index 5cc460899e2..7f5da5c3377 100644
--- a/ctdb/server/ctdb_monitor.c
+++ b/ctdb/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");
}