[SCM] CTDB repository - branch 1.2 updated - ctdb-1.0.114-267-gd7dbde5

[Ronnie Sahlberg]

The branch, 1.2 has been updated
       via  d7dbde5b6f92b556d5fa690ab260c717c5f97309 (commit)
      from  9b623ee64007aa1382189ff44a09ed62a26eda62 (commit)

http://gitweb.samba.org/?p=sahlberg/ctdb.git;a=shortlog;h=1.2


- Log -----------------------------------------------------------------
commit d7dbde5b6f92b556d5fa690ab260c717c5f97309
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date:   Fri Aug 20 14:54:03 2010 +1000

    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.

-----------------------------------------------------------------------

Summary of changes:
 server/ctdb_monitor.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


Changeset truncated at 500 lines:

diff --git a/server/ctdb_monitor.c b/server/ctdb_monitor.c
index 5cc4608..7f5da5c 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");
 	}
 


-- 
CTDB repository