<div dir="ltr"><br><br><div class="gmail_quote">On Wed, May 12, 2010 at 10:56 AM, Jan Wieck <span dir="ltr"><<a href="mailto:JanWieck@yahoo.com">JanWieck@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 5/12/2010 10:31 AM, Gurjeet Singh wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi All,<br>
<br>
I have two Slony test beds which show the exact same symptoms!<br>
<br>
select * from sl_event order by ev_seqno;<br>
<br>
ev_origin | ev_seqno | ev_timestamp | ev_snapshot | ev_type |<br>
-----------+------------+----------------------------+----------------------------+---------+-<br>
2 | 5000000002 | 2010-04-30 08:32:38.622928 | 458:458: | SYNC |<br>
1 | 5000525721 | 2010-05-12 13:30:22.79626 | 72685915:72685915: | SYNC |<br>
1 | 5000525722 | 2010-05-12 13:30:24.800943 | 72686139:72686139: | SYNC |<br>
1 | 5000525723 | 2010-05-12 13:30:26.804862 | 72686224:72686224: | SYNC |<br>
...<br>
<br>
</blockquote>
<br></div>
Slony always keeps at least the last event per origin around. Otherwise the view sl_status would not work.<br>
<br>
What should worry you is that there are no newer SYNC events from node 2 available. Slony does create a sporadic SYNC every now and then even if there is no activity or the node isn't an origin anyway.<br>
<br>
Is it possible that node 2's clock is way off?<br></blockquote><div><br><span style="font-family: courier new,monospace;"># ssh <a href="mailto:root@10.32.169.215">root@10.32.169.215</a> date; ssh <a href="mailto:root@10.32.169.216">root@10.32.169.216</a> date</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Wed May 12 16:38:20 UTC 2010</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Wed May 12 16:38:20 UTC 2010</span><br style="font-family: courier new,monospace;">
<br>Above the difference of times on the two nodes; 215 has the origin and 216 has the subscriber. They seem to be perfectly in sync.<br><br>I think I forgot to paste the <a href="http://test_slony_state.pl">test_slony_state.pl</a> output before. This is waht raised the concern<br>
<span style="font-family: courier new,monospace;"><snip></span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Node: 2 Confirmations not propagating from 2 to 1</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">================================================</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Confirmations not propagating quickly in sl_confirm -</span><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">For origin node 2, receiver node 1, earliest propagated</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">confirmation has age 12 days > 00:30:00</span><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Are slons running for both nodes?</span><br style="font-family: courier new,monospace;"><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Could listen paths be missing so that confirmations are not propagating?</span><br style="font-family: courier new,monospace;"><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Node: 2 Events not propagating to node 2</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">================================================</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Events not propagating quickly in sl_event -</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">For origin node 2, earliest propagated event of age 12 days 00:01:00 > 00:30:00</span><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Are slons running for both nodes?</span><br style="font-family: courier new,monospace;"><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Could listen paths be missing so that events are not propagating?</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"></snip></span><br style="font-family: courier new,monospace;">
<br>And the path and listen configs:<br><br><span style="font-family: courier new,monospace;">system.db=# select * from sl_path;</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> pa_server | pa_client | pa_conninfo | pa_connretry</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">-----------+-----------+---------------------------------------------------+--------------</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> 2 | 1 | dbname=system.db host=10.32.169.216 user=postgres | 10</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> 1 | 2 | dbname=system.db host=10.32.169.215 user=postgres | 10</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">(2 rows)</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">system.db=# select * from sl_listen ;</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> li_origin | li_provider | li_receiver</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">-----------+-------------+-------------</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> 2 | 2 | 1</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> 1 | 1 | 2</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">(2 rows)</span><br style="font-family: courier new,monospace;">
<br><br>Thanks and best regards,<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<br>
Jan<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
The reason I think this _might_ be a bug is that on both clusters, slave node's sl_event has the exact same record for ev_seqno=5000000002 except for the timestamp; same origin, and same snapshot!<br>
<br>
The head of sl_confirm has:<br>
<br>
select * from sl_confirm order by con_seqno;<br>
<br>
con_origin | con_received | con_seqno | con_timestamp<br>
------------+--------------+------------+----------------------------<br>
2 | 1 | 5000000002 | 2010-04-30 08:32:53.974021<br>
1 | 2 | 5000527075 | 2010-05-12 14:15:41.192279<br>
1 | 2 | 5000527076 | 2010-05-12 14:15:43.193607<br>
1 | 2 | 5000527077 | 2010-05-12 14:15:45.196291<br>
1 | 2 | 5000527078 | 2010-05-12 14:15:47.197005<br>
...<br>
<br>
Can someone comment on the health of the cluster? All events, except for that on, are being confirmed and purged from the system regularly, so my assumption is that the cluster is healthy and that the slave is in sync with the master.<br>
<br>
Thanks in advance.<br>
-- <br>
gurjeet.singh<br>
@ EnterpriseDB - The Enterprise Postgres Company<br>
<a href="http://www.enterprisedb.com" target="_blank">http://www.enterprisedb.com</a><br>
<br>
singh.gurjeet@{ gmail | yahoo }.com<br>
Twitter/Skype: singh_gurjeet<br>
<br>
Mail sent from my BlackLaptop device<br>
<br>
<br></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Slony1-general mailing list<br>
<a href="mailto:Slony1-general@lists.slony.info" target="_blank">Slony1-general@lists.slony.info</a><br>
<a href="http://lists.slony.info/mailman/listinfo/slony1-general" target="_blank">http://lists.slony.info/mailman/listinfo/slony1-general</a><br>
</blockquote>
<br>
<br>
-- <br>
Anyone who trades liberty for security deserves neither<br>
liberty nor security. -- Benjamin Franklin<br>
</blockquote></div><br><br clear="all"><br>-- <br>gurjeet.singh<br>@ EnterpriseDB - The Enterprise Postgres Company<br><a href="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br><br>singh.gurjeet@{ gmail | yahoo }.com<br>
Twitter/Skype: singh_gurjeet<br><br>Mail sent from my BlackLaptop device<br>
</div>