Dont set next_interval to 0.
authorRonnie Sahlberg <ronniesahlberg@gmail.com>
Fri, 20 Aug 2010 04:54:03 +0000 (14:54 +1000)
committerRonnie Sahlberg <ronniesahlberg@gmail.com>
Fri, 20 Aug 2010 04:54:03 +0000 (14:54 +1000)
commitd7dbde5b6f92b556d5fa690ab260c717c5f97309
treec7a5e759436ecd208d342547c1ae9b4db7a0ec7e
parent9b623ee64007aa1382189ff44a09ed62a26eda62
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