Thu Sep 27 14:40:46 PDT 2012
- Previous message: [Slony1-general] Issue when adding node to replication
- Next message: [Slony1-general] Issue when adding node to replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/27/2012 5:30 PM, Christopher Browne wrote: > On Thu, Sep 27, 2012 at 5:26 PM, Jan Wieck <JanWieck at yahoo.com> wrote: >> My guess is that the right solution to this is to clean out everything >> again when a STORE NODE comes along. We had been thinking of making the >> node ID non-reusable to prevent this sort of race conditions. > > I'm not sure I'm totally comfortable with cleaning it all out > instantly; as a step towards that, I'd think it a good idea for slonik > to check all the nodes for existence of a node ID, and refuse if it's > found anywhere. > > Under that circumstance, you might need to wait, to run the STORE > NODE, until the cleanup thread has run on all the nodes to expunge the > last bits of the node on all nodes' databases. > > Smells a bit safer to me... > Check cleanupEvent(). I think it will never remove that stale event. Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] Issue when adding node to replication
- Next message: [Slony1-general] Issue when adding node to replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list