December 22, 2009 at 11:34 am
Hi,
I have peer 2 peer replication within 4 server's.
There are 2 DB's with 2 Peer 2 Peer replication so far since 1 year everything was working fine.
As we are DBA's our problem increase when the Data Increases so is mine rite know.
So looking for any Suggestion or help which would be highly appreciated.
Issue is
As there are 2 Publication with 3 subscriber's each.
There are 2 Log reader agent job.
And when i do sp_who2 i see 3 Log reader for each publication wiht same agent id.
So I assumed might be 3 subscription so 3 log reader.
But 1 publication is holding lock on another publication
As it needs to write commands in Distribution db and meanwhile Distribution clean up runs every 10 mins
Its locking the whole replication process make another log reader agent waiting on to finish and bcoz of this the Publication DB Log file is getting filled up.
So far there was no issues i scratch the replication for 1 DB and recreated but issue still exists.
If anyone has came across this situation please let me konw what to do .
Thanks
December 29, 2009 at 1:59 pm
Just need a tad more information. Is the Distribution Cleanup job which deletes from MSRepl_commands table blocking the log reader(s)? or is each log reader blocking each other?
December 29, 2009 at 2:41 pm
I suspected the same but I did disabled the Cleanup agent job and observed the both LogReader agents block eachother.
Stoped 1 log reader and observed enabling AgentClean up job and everything worked fine there was a blocking when Agent cleanup job was running but its usual and locks got realased after 3 4 mins thats a usual behaviour.
But I did see logreader sp's which selects command from distribution and inserts is getting blocked.The same setup runs smooth on another server.
I suspect may be due to heavy data but aint sure.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply