glusterfs.git/xlators/features/marker/utils/syncdaemon/gsyncd.py, branch v3.2.1

syncdaemon: some refactor on monitor

2011-05-31T17:01:41+00:00

- detect faulty state early
- keep the feedback fd in gsyncd module

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2537 (gsync autorestart)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2537

BUG: 2537 (gsync autorestart)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2537

syncdaemon: have the monitor kill the worker if it does not connect in 60 sec

2011-04-22T11:05:20+00:00

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

syncdaemon: add session-owner option

2011-04-19T09:30:38+00:00

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2785 (gsyncd logs on slave side go to /dev/null)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

syncdaemon: implement template substitutions for config values

2011-04-19T09:30:32+00:00

So, for example, a log file setting of

  /var/log/${mastervol}/${eSlave}.log

will be substituted with the volume name of the master and the
canonicalized-escaped name of the slave for each master-slave pair.

As template expanders, beyond the various forms and derivatives
of master and slave, the following are also available:
 - gsyncd tunables (set in command line or in config)
 - for regexp sections, regexp group captures can be accessed
   via "match_", where i=1,2 corresponds to the i-th peer-rx
   in the section title and n=1,... to the n-th capture.

This will enable us to have a static configuration (not having to
add new entries on each gsyncd start).

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2785 (gsyncd logs on slave side go to /dev/null)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

syncdaemon: fix swallowing of exit value

2011-04-19T09:30:03+00:00

Signed-off-by: Csaba Henk Signed-off-by: Anand Avati BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

syncdaemon: minor cleanups on termination

2011-04-17T14:39:15+00:00

Signed-off-by: Csaba Henk Signed-off-by: Anand Avati BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

syncdaemon: yet another try to exit properly

2011-04-16T11:10:32+00:00

The final cleanup sequence + call to _exit, which was just done in the main thread, now is called for in each thread when the thread crashes. Seems we aren't left there hanging this way. Signed-off-by: Csaba Henk Signed-off-by: Anand Avati BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

syncdaemon: ensure -/_ invariance in tunables, in all components

2011-04-13T11:43:14+00:00

Signed-off-by: Csaba Henk Signed-off-by: Anand Avati BUG: 2659 (gsync config-del option is not working properly) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2659

syncdaemon: refactor gsyncd.py cmdline interface to configuration

2011-04-13T11:43:10+00:00

- existence of given tunable is checked - add --config-check option to just do a check for existence of tunable Signed-off-by: Csaba Henk Signed-off-by: Anand Avati BUG: 2659 (gsync config-del option is not working properly) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2659

syncdaemon: force termination for unhandled exception in any thread

2011-04-13T11:43:06+00:00

Signed-off-by: Csaba Henk Signed-off-by: Anand Avati BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736