Tue Mar 15 14:48:44 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=200 Summary: slon_retry() overused Product: Slony-I Version: devel Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: medium Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: cbbrowne at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 Noticed in bug #175... There are a LOT of places where slon_retry() is called, which signals a start of the slon daemon. local_listener.c: 8 cleanup_thread.c: 4 remote_worker.c: 45 sync_thread.c: 5 misc.c: 3 runtime_config.c: 15 slon.c: 15 This seems rather excessive - if a problem occurs in any of these places, this effectively terminates all activity that's going on. If a 2-day-long subscription is taking place, then any little problem that occurs in a peripheral area will take that down and restart it. Some assessment should take place to determine the degree to which this is excessive. There are legitimately problems that are fatal that warrant terminating/restarting the slon daemon. But probably not *quite* this many... -- 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. You are the assignee 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