"Davec" <dcowie@ballsolutions.com> wrote in message
news:1148907183.888736.320310@y43g2000cwc.googlegroups.com...
> Hi all,
>
> I have set up 10 subscribers each with merge pull subscriptions. the
> polling interval is 60 seconds and the StartQueueTimeout 120 seconds.
> I have limited the number of concurrent merge processes to 5 however
> the problem is that it seems the 5 that queue up never get a look in
> even even though the status of the 5 which started first are now idle.
>
> When one of the idle merege processes is manually stoped the next in
> the queue takes its place. It is behaving as though the merge process
> is still active. Even with Startqueuetimeout set to 0 (indefinite)
> wait it will never get its time to participate in the merge.
>
>
> A simple test of 2 subscribers and a limit of one concurrent merge
> process also exhibits same promlem. showing blocking between the two
> processes every time. last command to execute sp_MSAquireSlotLock
>
> Is there some fundemental thing i am missing because this cannot be
> normal?
>

"Davec" <dcowie@ballsolutions.com> wrote in message
news:1148938343.909297.290020@j73g2000cwa.googlegroups.com...
> Hi Hilary,
>
> ok that would not be good for me. i have read plenty of other posts
> in this group that seem to referenct concurrent merge processes on the
> context of Continuous merge. You made a post on the 19 Jan 2006 Titled
> Merge Replication limit running in continuous mode. which i guess has
> me a little confused. In that article you talked about limiting the
> number of concurrent merege process.
>
> I have ended up with continuus mode because of the larger bandwidth
> overheads associated with starting scheduled merge jobs every 1 minute.
> (Approx 118K of overhead data is cteated eachtime a subscriber
> executes the the merge job).
>
> So assuming my only option is to run in continuous mode with a polling
> interval of 60 is there any way to contoll the number of merge jobs
> executing at any one time. It absolutely hammers the publ;ishers
> processor resulting in slowed mereg jobs.
>
>
> Thanks
>

> Hi all,
>
> I have set up 10 subscribers each with merge pull subscriptions. the
> polling interval is 60 seconds and the StartQueueTimeout 120 seconds.
> I have limited the number of concurrent merge processes to 5 however
> the problem is that it seems the 5 that queue up never get a look in
> even even though the status of the 5 which started first are now idle.
>
> When one of the idle merege processes is manually stoped the next in
> the queue takes its place. It is behaving as though the merge process
> is still active. Even with Startqueuetimeout set to 0 (indefinite)
> wait it will never get its time to participate in the merge.
>
>
> A simple test of 2 subscribers and a limit of one concurrent merge
> process also exhibits same promlem. showing blocking between the two
> processes every time. last command to execute sp_MSAquireSlotLock
>
> Is there some fundemental thing i am missing because this cannot be
> normal?
>