git.samba.org / metze / ctdb / wip.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6488651) | patch
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 05:00:45 +0000 (15:00 +1000)
commit92c8408fba957a8ded13f7e285da290502735234
treea10df5853c24580f1eae90d4231e7f9b289b5f2btree
parent6488651aa7e105c57324f4a300760a010d098fbbcommit | diff
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 diff | blob | history
Work in progress branches