So I started this thread on the slon forum, and they mentioned that I/we should ask here.<br /><br />Postgres 9.1.4
slon2.1.1<br />-and-<br />Postgres 9.1.6 slon 2.1.2<br /><br />Scenario:<br /><br />Node 1, is on gig circut and is the
master (West Coast)<br /><br />Node 2, is also on a gig circuit and is the slave (Georgia)<br /><br />Symptoms, slon
immediatelydies after transferring the biggest table in the set (this happens with 2 of 3 sets, the set that actually
completeshas no large tables).<br /><br />Set 1 has a table that takes just under 6000 seconds, and set 2 has a table
thattakes double that, and again it completes.<br /><br />1224459-2013-01-11 14:21:10 PST CONFIG remoteWorkerThread_1:
5760.913seconds to copy table "cls"."listings"<br />1224560-2013-01-11 14:21:10 PST CONFIG remoteWorkerThread_1: copy
table"cls"."customers"<br /> 1224642-2013-01-11 14:21:10 PST CONFIG remoteWorkerThread_1: Begin COPY of table
"cls"."customers"<br/>1224733-2013-01-11 14:21:10 PST ERROR remoteWorkerThread_1: "select
"_admissioncls".copyFields(8);" <--- this has the proper data<br /> 1224827:2013-01-11 14:21:10 PST WARN
remoteWorkerThread_1:data copy for set 1 failed 1 times - sleep 15 seconds<br /><br />Now in terms of postgres, if I do
acopy from node 1 to node 2 the large table (<2 hors) completes without issue.<br /><br />From Node 2:<br
/>-bash-4.1$psql -h idb02 -d admissionclsdb -c "copy cls.listings to stdout" | wc<br /> 4199441 600742784
6621887401<br/><br />This worked fine.<br /><br />I get no errors in the postgres logs, there is no network disconnect
andsince I can do a copy over the wire that completes, I'm at a loss. I don't know what to look at, what to look for
orwhat to do. Obviously this is the wrong place to slon issues.<br /><br />One of the slon developers stated;<br />"I
wonderif there's something here that should get bounced over to<br /> pgsql-hackers or such; we're poking at a scenario
herewhere the use<br /> of <span>COPY</span> to stream <span>data</span> between systems is proving troublesome, and<br
/>perhaps there may be meaningful opinions over there on that."<br /><br />If a copy of the same table that seems to be
atthe end of a slon failed attempt and it will complete with a copy, I'm just not sure what is going on.<br /><br />Any
suggestions,please ask for more data, I can do anything to the slave node, it's a bit tougher on the source, but I can
arrangeto make changes to it if need be.<br /><br /><br />I just upgraded to 9.1.6 and slon 2.1.2 but prior tests were
on9.1.4 and slon 2.1.1 and a mix of postgres 9.1.4 slon 2.1.1 and postgres 9.1.6 slon 2.1.1 (node 2)<br /><br />The
otherdifference is node 1 is running on Fedora12 and node 2 is running CentOS 6.2<br /><br />Thanks in advance<br
/>Tory<br/>