Tue Mar 15 10:17:30 PDT 2011
- Previous message: [Slony1-bugs] [Bug 175] Monitoring cluster better
- Next message: [Slony1-bugs] [Bug 175] Monitoring cluster better
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=175 --- Comment #10 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-03-15 10:17:30 PDT --- Per Steve Singer: <http://lists.slony.info/pipermail/slony1-hackers/2011-March/000446.html> A general comment: This monitor thread calls slon_retry() a bunch of times. We've created a whole bunch of new failure points for slon. I'm not sure issues recording the monitor state should result in a slon falling over. I feel that if the monitor thread hits an error it can reset the database connections for the monitor thread but it should leave the threads doing real work alone. Having said that we might also want a maximum size of the queue. If the queue exceeds a certain size (maybe because the monitor thread keeps hitting issues) then we stop putting new elements on the queue or discard the oldest ones. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
- Previous message: [Slony1-bugs] [Bug 175] Monitoring cluster better
- Next message: [Slony1-bugs] [Bug 175] Monitoring cluster better
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list