|
Home > Archive > Slony1 PostgreSQL Replication > January 2006 > check_slony_cluster not particularly effective:
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
check_slony_cluster not particularly effective:
|
|
| Marc G. Fournier 2005-12-31, 1:23 pm |
|
# ./check_slony_cluster.sh dns ams localhost
Password for user pgsql:
OK - 3 nodes in sync
2 of the 3 nodes weren't even running, nor have been for >24 hours ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy-rZG+BmoqAtU@public.gmane.org Yahoo!: yscrappy ICQ: 7615664
| |
| John Sidney-Woollett 2006-01-03, 7:23 am |
| Hmm, I wrote the original version of that script - it's just designed to
determine whether active slon subscribers are keeping up.
I also use the separate check_slon on each node to determine whether the
slon process is actually running or not.
In other words you need to use the check_slony_cluster against the
master database, and the check_slon for each node.
I don't know enough about slon to determine whether you can check the
whole replication array and nodes using the (master) database alone.
If you discover that you can, please could you post any ammendments for
either script.
Thanks
John
Marc G. Fournier wrote:
>
> # ./check_slony_cluster.sh dns ams localhost
> Password for user pgsql:
> OK - 3 nodes in sync
>
> 2 of the 3 nodes weren't even running, nor have been for >24 hours ...
>
> ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy-rZG+BmoqAtU@public.gmane.org Yahoo!: yscrappy ICQ: 7615664
> ____________________
____________________
_______
> Slony1-general mailing list
> Slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
> http://gborg.postgresql.org/mailman.../slony1-general
| |
| Vivek Khera 2006-01-03, 11:24 am |
|
On Jan 3, 2006, at 7:08 AM, John Sidney-Woollett wrote:
> I don't know enough about slon to determine whether you can check the
> whole replication array and nodes using the (master) database alone.
>
> If you discover that you can, please could you post any ammendments
> for
> either script.
The sl_status view tells you everything from the master node.
|
|
|
|
|