http://www.slony.info/bugzilla/show_bug.cgi?id=23

           Summary: slon ignores maximum SYNC group size (-g option)
           Product: Slony-I
           Version: 1.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: medium
         Component: slon
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: jpfletch at ca.afilias.info
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


In testing slon v. 1.2.12, I have noticed that slon ignores the value provided
for  'maximum SYNC group size', either when supplied on the command line via
the -g switch, or via configuration parameter 'sync_group_maxsize'.  

When run from the commnad line via:

slon -d 2 -g 10 clustername "host=host2 port=9533 user=slony dbname=dbname"

i see the following patterns of SYNC grouping:

2007-12-03 16:48:58 UTC DEBUG2 remoteWorkerThread_8143: SYNC 280132 done in
35.906 seconds
2007-12-03 16:50:01 UTC DEBUG2 remoteWorkerThread_8143: SYNC 280195 done in
62.948 seconds
2007-12-03 16:52:20 UTC DEBUG2 remoteWorkerThread_8143: SYNC 280322 done in
139.665 seconds
2007-12-03 16:56:50 UTC DEBUG2 remoteWorkerThread_8143: SYNC 280550 done in
269.685 seconds
2007-12-03 17:02:20 UTC DEBUG2 remoteWorkerThread_8143: SYNC 280846 done in
319.656 seconds


If I'm interpreting this correctly, the slon applied a group of 63 SYNCs, then
127, then 228, then 296.

This testcase involves the subscriber node being behind, initially by 200
SYNCs, then starting a slon to observe the behavior during catch-up.  I'm not
certain that the slon's behavior here is bad (i.e. it might be doing the
smartest thing), however, the command line switch should either work, or be
deprecated.


-- 
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.