Fri Jan 30 08:18:04 PST 2009
- Previous message: [Slony1-general] Re: pg_config for slony1 install
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
My cluster has gone out of sync since I added another node.
The setup has one master and two slaves. The master can connect both =
slaves but each of the slaves can only connect to the master not the =
other slave.
Is this setup feasible?
The Master has a store path for each of the slaves. But the slaves have =
only one to the master.
But each node Listens every other. This was created by the slonik =
command subscribe set.
Am I right in assuming that listen does not necessaryly implies dorect =
db connection aka. store path?
I could make a connection between the nodes, but I would prefer not to. =
Especially because it would need VPN setups into networks outside of our =
company.
I have attached the output of test_slony_state-dbi.pl
-- =
Tilman Baumann
Software Developer
Collax GmbH . Boetzinger Strasse 60 . 79111 Freiburg . Germany
p: +49 (0) 89-990157-0
f: +49 (0) 89-990157-11
Geschaeftsfuehrer: Boris Nalbach
AG Muenchen HRB 158898, Ust.-IdNr: DE 814464942
-------------- next part --------------
DSN: dbi:Pg:dbname=3Dlicenseserver;host=3D172.16.64.5;port=3D5432;user=3Dli=
censeserver;password=3DXXX
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Rummage for DSNs
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
Query:
select p.pa_server, p.pa_conninfo
from "_licenseserver_cluster".sl_path p
-- where exists (select * from "_licenseserver_cluster".sl_subscribe s wh=
ere
-- (s.sub_provider =3D p.pa_server or s.sub_receiv=
er =3D p.pa_server) and
-- sub_active =3D 't')
group by pa_server, pa_conninfo;
Tests for node 4 - DSN =3D dbname=3Dlicenseserver host=3D172.16.254.7 port=
=3D5432 user=3Dlicenseserver password=3DXXX
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
pg_listener info:
Pages: 16
Tuples: 2
Size Tests
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
sl_log_1 19 692.000000
sl_log_2 28 266.000000
sl_seqlog 1910 275820.000000
Listen Path Analysis
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
No problems found with sl_listen
---------------------------------------------------------------------------=
-----
Summary of event info
Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
3 1073918 1073918 2 days 01:54:00 2 days 01:54:00 1
1 920955 990060 00:00:00 8 days 01:44:00 0
4 1 35015 00:00:00 4 days 05:26:00 0
---------------------------------------------------------------------------=
------
Summary of sl_confirm aging
Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of elde=
st SYNC
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
1 3 920955 920955 8 days 01:44:00 8 days 01:44:0=
0 1
1 4 989563 989563 01:23:00 01:23:00 1
3 1 1073918 1073918 2 days 01:54:00 2 days 01:54:0=
0 1
3 4 1073918 1073918 2 days 01:54:00 2 days 01:54:0=
0 1
4 1 34946 35015 00:00:00 00:11:00 0
4 3 0 0 4 days 05:26:00 4 days 05:26:0=
0 1
---------------------------------------------------------------------------=
---
Listing of old open connections
Database PID User Query Age =
Query
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Tests for node 1 - DSN =3D dbname=3Dlicenseserver host=3D172.16.64.5 port=
=3D5432 user=3Dlicenseserver password=3DXXX
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
pg_listener info:
Pages: 16
Tuples: 2
Size Tests
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
sl_log_1 19 692.000000
sl_log_2 28 266.000000
sl_seqlog 1910 275820.000000
Listen Path Analysis
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
No problems found with sl_listen
---------------------------------------------------------------------------=
-----
Summary of event info
Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
3 1073918 1073918 2 days 01:54:00 2 days 01:54:00 1
1 920955 990060 00:00:00 8 days 01:44:00 0
4 1 35015 00:00:00 4 days 05:26:00 0
---------------------------------------------------------------------------=
------
Summary of sl_confirm aging
Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of elde=
st SYNC
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
1 3 920955 920955 8 days 01:44:00 8 days 01:44:0=
0 1
1 4 989563 989563 01:23:00 01:23:00 1
3 1 1073918 1073918 2 days 01:54:00 2 days 01:54:0=
0 1
3 4 1073918 1073918 2 days 01:54:00 2 days 01:54:0=
0 1
4 1 34946 35015 00:00:00 00:11:00 0
4 3 0 0 4 days 05:26:00 4 days 05:26:0=
0 1
---------------------------------------------------------------------------=
---
Listing of old open connections
Database PID User Query Age =
Query
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Tests for node 3 - DSN =3D dbname=3Dlicenseserver host=3D172.16.254.5 port=
=3D5432 user=3Dwww72 password=3DXXX
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
pg_listener info:
Pages: 16
Tuples: 2
Size Tests
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
sl_log_1 19 692.000000
sl_log_2 28 266.000000
sl_seqlog 1910 275820.000000
Listen Path Analysis
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
No problems found with sl_listen
---------------------------------------------------------------------------=
-----
Summary of event info
Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
3 1073918 1073918 2 days 01:54:00 2 days 01:54:00 1
1 920955 990060 00:00:00 8 days 01:44:00 0
4 1 35015 00:00:00 4 days 05:26:00 0
---------------------------------------------------------------------------=
------
Summary of sl_confirm aging
Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of elde=
st SYNC
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
1 3 920955 920955 8 days 01:44:00 8 days 01:44:0=
0 1
1 4 989563 989563 01:23:00 01:23:00 1
3 1 1073918 1073918 2 days 01:54:00 2 days 01:54:0=
0 1
3 4 1073918 1073918 2 days 01:54:00 2 days 01:54:0=
0 1
4 1 34946 35016 00:00:00 00:11:00 0
4 3 0 0 4 days 05:26:00 4 days 05:26:0=
0 1
---------------------------------------------------------------------------=
---
Listing of old open connections
Database PID User Query Age =
Query
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Sending message thus - |/usr/bin/nail -s "Slony State Test Warning - Cluste=
r licenseserver_cluster" tilman.baumann at collax.com
Message:
Node: 1 sl_seqlog tuples =3D 275820 > 200000
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Number of tuples in Slony-I table sl_seqlog is 275820 which
exceeds 200000.
You may wish to investigate whether or not a node is down, or perhaps
if sl_confirm entries have not been propagating properly.
Node: 3 sl_seqlog tuples =3D 275820 > 200000
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Number of tuples in Slony-I table sl_seqlog is 275820 which
exceeds 200000.
You may wish to investigate whether or not a node is down, or perhaps
if sl_confirm entries have not been propagating properly.
Node: 4 sl_seqlog tuples =3D 275820 > 200000
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Number of tuples in Slony-I table sl_seqlog is 275820 which
exceeds 200000.
You may wish to investigate whether or not a node is down, or perhaps
if sl_confirm entries have not been propagating properly.
- Previous message: [Slony1-general] Re: pg_config for slony1 install
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list