Hi
Nothing
of that; but we had one of the slave down for last 8 days and still in
subscribe list. Do you think that has an effect on the other nodes ?
st_origin
| st_received | st_last_event | st_last_event_ts |
st_last_received | st_last_received_ts |
st_last_received_event_ts | st_lag_num_events | st_lag_time
-----------+-------------+---------------+----------------------------+------------------+----------------------------+----------------------------+-------------------+------------------------
45 | 60 | 5001958753 | 2012-02-22 21:32:02.555943 |
5001566396 | 2012-02-13 19:09:04.346031 | 2012-02-13 12:28:53.968515
| 392357 | 9 days 09:03:09.219735
45 | 67 | 5001958753 | 2012-02-22 21:32:02.555943 |
5001949595 | 2012-02-22 20:47:55.672691 | 2012-02-22 16:18:10.759348
| 9158 | 05:13:52.428902
45 | 66 | 5001958753 | 2012-02-22 21:32:02.555943 |
5001930109 | 2012-02-22 20:46:02.378948 | 2012-02-22 04:19:30.589199
| 28644 | 17:12:32.599051
________________________________
From: Vick Khera <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Wednesday, February 22, 2012 4:28 AM
Subject: Re: [Slony1-general] Replication Lag - fetch 500 from LOG
On Tue, Feb 21, 2012 at 10:30 PM, Brian Trudal <[email protected]> wrote:
> Anything that am missing ?
Has your query (mostly write) load changed? Did one of your disks in
your array die? You should poke around to see if you're saturating
either your network or one of the servers' disk I/O bandwidth.
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
