June 23, 2015 at 4:22 am
Hi,
I have two subscribers to a database replication. One in a data center 200 miles away and the other subscriber in the same rack.
When I insert a tracer token it takes 7 secs to get to the server 200 miles away but 30 mins to get to the one in the same rack.
how can I investigate why replication is so slow on the second server. Ping connectively is less than 1ms.
June 23, 2015 at 6:47 am
steve.roberts 86619 (6/23/2015)
Hi,I have two subscribers to a database replication. One in a data center 200 miles away and the other subscriber in the same rack.
When I insert a tracer token it takes 7 secs to get to the server 200 miles away but 30 mins to get to the one in the same rack.
how can I investigate why replication is so slow on the second server. Ping connectively is less than 1ms.
A couple of thoughts:
1.) Have you reviewed the configuration of each "remote" server looking for differences?
----a.) network configuration
----b.) definition for the replication source
2.) Overall load on the remote server, including I/O Wait time.
3.) Available RAM on the remote server, including any queue length info.
Those are just some things I'd go looking for. Also look for DNS aliases that might have some routing impact.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
June 23, 2015 at 8:10 am
hi sorry what does this mean?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply