Thu Nov 29 20:23:57 PST 2012
- Previous message: [Slony1-general] data copy for set 1 failed 3 times - sleep 60 seconds
- Next message: [Slony1-general] data copy for set 1 failed 3 times - sleep 60 seconds
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Well this is frustrating. So I was successful in replicating a smaller data
set without issue. Once I try to replicate large amounts of data , it seems
to fail and restart, at what it feels the end of the biggest table of each
set.
2012-11-29 19:54:06 PST CONFIG remoteWorkerThread_1: 16341.883 seconds to
copy table "tracking"."spotimpressions"
2012-11-29 19:54:06 PST CONFIG remoteWorkerThread_1: copy table
"tracking"."impressions"
2012-11-29 19:54:06 PST CONFIG remoteWorkerThread_1: Begin COPY of table
"tracking"."impressions"
2012-11-29 19:54:06 PST ERROR remoteWorkerThread_1: "select
"_admissioncls".copyFields(19);"
2012-11-29 19:54:06 PST WARN remoteWorkerThread_1: data copy for set 2
failed 1 times - sleep 15 seconds
This large table ran for 4+ hours and the minute it starts with the very
next table, it "fails", Identical behavior when doing set 1 which has a
large table
1235574-2012-11-29 12:22:12 PST CONFIG remoteWorkerThread_1: Begin COPY of
table "cls"."customers"
1235665-2012-11-29 12:22:12 PST ERROR remoteWorkerThread_1: "select
"_admissioncls".copyFields(8);"
1235759:2012-11-29 12:22:12 PST WARN remoteWorkerThread_1: data copy for
set 1 failed 1 times - sleep 15 seconds
Followed sometime later by this
2012-11-29 12:22:28 PST DEBUG2 remoteWorkerThread_2: forward confirm
3,5001168772 received by 4
2012-11-29 12:22:28 PST INFO copy_set 1 - omit=f - bool=0
2012-11-29 12:22:28 PST INFO omit is FALSE
So what's going on, it appears to have made it through the heavy lifting,
but it immediately goes to fail as it starts a much smaller table. Why does
it wait to make it through the largest table in the set, before it says
"bahh just kidding".
AHHH interesting, yet again at the moment of "fail" a log switchover is
starting, this is identical to each and every failure. Why is a log switch
appearing right before every failure?!
Can I disable this for a test? , disable logswitch
2012-11-29 19:54:11 PST admissionclsdb postgres [local] NOTICE: Slony-I:
Logswitch to sl_log_2 initiated
2012-11-29 19:54:11 PST admissionclsdb postgres [local] CONTEXT: SQL
statement "SELECT "_admissioncls".logswitch_start()"
PL/pgSQL function "cleanupevent" line 96 at PERFORM
2012-11-29 12:22:13 PST admissionclsdb postgres [local] NOTICE: Slony-I:
Logswitch to sl_log_2 initiated
2012-11-29 12:22:13 PST admissionclsdb postgres [local] CONTEXT: SQL
statement "SELECT "_admissioncls".logswitch_start()"
PL/pgSQL function "cleanupevent" line 96 at PERFORM
"
Thanks
Tory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20121129/c167a273/attachment.htm
- Previous message: [Slony1-general] data copy for set 1 failed 3 times - sleep 60 seconds
- Next message: [Slony1-general] data copy for set 1 failed 3 times - sleep 60 seconds
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list