Fri Feb 18 15:57:59 PST 2005
- Previous message: [Slony1-general] replication stalled -- listen's can't be re-inserted
- Next message: [Slony1-general] replication stalled -- listen's can't be re-inserted
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Vivek Khera wrote: > hi guys... i've got my replication stalled... here's what I did. > > my provider is node2. receiver is node 1. i added a new receiver > node3 subscribed via node 1. > > once all caught up, I moved node 3 to subscribe from node 2, waited a > while, then moved node 1 to subscribe from node 3. after a little > more time, I then dropped node 1. all the listen entries seem to have > disappeared: sl_listen is empty. > > I ran these slonik commands: > > store listen (origin = 2, receiver = 3, provider = 2); > store listen (origin = 3, receiver = 2, provider = 3); > > but sl_listen only shows the provider=3 receiver=2 listen, but it is > refusing to add the provider=2 receiver=3 listen. no errors from slonik. > > can I just insert into the sl_listen table directly? The problem here is almost certainly that the event to add that listen is waiting on, um, probably node 3. I would be very disinclined to add entries directly; I'm "allergic" to messing around with the tables directly :-). I would instead go to the node with empty sl_listen and do: -# select _somecluster.storelisten(2,3,2), _somecluster.storelisten(3,2,3); That will add both entries on that node, and propagate the event to add them everywhere else. If the event doesn't make it to the other node, then you might run the same query there, too. (Substituting the namespace in YOUR system for "_somecluster", of course.)
- Previous message: [Slony1-general] replication stalled -- listen's can't be re-inserted
- Next message: [Slony1-general] replication stalled -- listen's can't be re-inserted
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list