On 10-11-09 07:13 PM, Richard Yen wrote:
> Hmm, that seems to make sense.  Given that Daylight Savings Time just
> ended, that might explain the reason why it got abandoned, since my slon
> procs run on a central/remote server
>
> Leads me to a separate question: are there pros/cons to running the slon
> app on a remote server rather than on the local server?  Seems like it
> makes administration easer--but at the cost of increased network traffic?
>
> Do you have any insight to this?

Administration is easier, it MIGHT simplify your security procedures 
(you could have all the db servers 'trust' one admin server or have a 
.pgpass file in the one admin server instead of passwords spread out 
everywhere).   But it will increase network traffic.

I'd say that at a minimum I would try to have the slon running on the 
same LAN segment as the database instance it is serving.  The latency of 
running slon over a WAN might be an issue + slon does not deal well with 
network outages that tend to be more common on a WAN.

Our dba team tends to run the slons from central admin servers and I 
think they are happy with how it works out.


>
> --Richard
>
> On Tue, Nov 9, 2010 at 2:38 PM, Steve Singer <ssinger at ca.afilias.info
> <mailto:ssinger at ca.afilias.info>> wrote:
>
>     On 10-11-09 11:09 AM, Richard Yen wrote:
>
>         Hi, does anyone know if slony ever "abandons" connections?  I've
>         had an
>         idle transaction for the past 6 hours on one of my subscriber nodes,
>         and according to my logs, the transaction was started, but there was
>         never any action done in it, except to set the transaction level to
>         serializable
>
>         Odd thing is--the node is not lagging from the origin when I
>         look at the
>         origin's sl_status table
>
>         Also, I don't know if this might be relevant, but the backend
>         for the
>         transaction has been open since 2010-11-01, and it's been processing
>         plenty of transactions successfully up until this point
>
>         How else can I diagnose this problem?
>         --Richard
>
>
>
>     First I would determine which slon process the connection comes from
>     (pg_stat_activity matched to the process id).
>
>     If the slon is the 'local' to the slave database (that is, this is
>     the slon servicing the node that is reporting the idle connection)
>     then you need to figure out which thread the has stopped.
>
>     Have you changed the time/date on your server recently?
>     Do you see traffic in the logs from localListener, cleanupThread?
>     the sync thread?
>
>
>     If it is a remote connection, then what was the last thing that
>     remote listener did.
>
>     Slony doesn't normally abandon connections but it is possible
>     something went wrong.
>
>
>
>
>
>
>
>         _______________________________________________
>         Slony1-general mailing list
>         Slony1-general at lists.slony.info
>         <mailto:Slony1-general at lists.slony.info>
>         http://lists.slony.info/mailman/listinfo/slony1-general
>
>
>