Re: [Slony1-general] slony1 drop node failure

Checked the logs for our other replicas. Details below. With a 6-7 sec gap, it’s less clear how the problem would have come from those. Reproducing this would probably be hard. This is the first time it’s ever happened for us. On the theory there is a race condition, one way to

Re: [Slony1-general] slony1 drop node failure

On Mon, 26 Feb 2018, Tignor, Tom wrote: In the slony1 log of our primary host (the same one which later showed the bug) we had: 2018-02-21 19:19:49 UTC [22582] INFO remoteWorkerThread_8: SYNC 5002075962 done in 1.725 seconds 2018-02-21 19:19:50 UTC [22582] CONFIG disableNode:

Re: [Slony1-general] slony1 drop node failure

In the slony1 log of our primary host (the same one which later showed the bug) we had: 2018-02-21 19:19:49 UTC [22582] INFO remoteWorkerThread_8: SYNC 5002075962 done in 1.725 seconds 2018-02-21 19:19:50 UTC [22582] CONFIG disableNode: no_id=8 The timestamp of the problem

Re: [Slony1-general] slony1 drop node failure

On Mon, 26 Feb 2018, Tignor, Tom wrote: Thanks. I see the deletes added for sl_seqlog and sl_log_script. The constraint violation appearing in the errors was for sl_event. Do we expect these changes fully remove all state, including sl_event? The checkNodeDeleted function doesn’t look at

Re: [Slony1-general] slony1 drop node failure

Thanks. I see the deletes added for sl_seqlog and sl_log_script. The constraint violation appearing in the errors was for sl_event. Do we expect these changes fully remove all state, including sl_event? The checkNodeDeleted function doesn’t look at sl_event. Tom( On

Re: [Slony1-general] slony1 drop node failure

On Mon, 26 Feb 2018, Tignor, Tom wrote: You can get it from the github branch (latest commit) at https://github.com/ssinger/slony1-engine/tree/bug375 Steve, The patch link actually goes to a page which says “Bugzilla is down for maintenance.” Is there a way to see the

Re: [Slony1-general] slony1 drop node failure

Steve, The patch link actually goes to a page which says “Bugzilla is down for maintenance.” Is there a way to see the patch currently? Does it exist or is it scheduled in some Slony-I release? Tom( On 2/22/18, 6:06 PM, "Steve Singer" wrote:

Re: [Slony1-general] slony1 drop node failure

Wow. Yes, this looks a lot like the tmblue 9/10/16 event. I’ll be very interested to take a look at that patch. Haven’t forgotten the 2.2.6 patches I have in flight. Need to finish some other work and pull those off the back burner… Thanks, Tom( On

Re: [Slony1-general] slony1 drop node failure

On Thu, 22 Feb 2018, Tignor, Tom wrote: Looks like? http://lists.slony.info/pipermail/slony1-general/2016-September/013331.html I can't remember if that was what prompted http://lists.slony.info/pipermail/slony1-hackers/2016-December/000560.html