On 24 August 2015 at 17:03, Steve Singer <[email protected]> wrote:
> On 08/24/2015 04:58 PM, Dave Cramer wrote: > >> >> On 24 August 2015 at 16:57, Steve Singer <[email protected] >> <mailto:[email protected]>> wrote: >> >> On 08/24/2015 04:12 PM, Dave Cramer wrote: >> >> I am currently waiting on a resubscribe event. How does slony >> get this >> event through all the backlog events ? >> >> >> Usually pretty quickly. >> Slonik waits for the provider to be caught up before submitting the >> event. >> >> The question is, why is your provider behind? Is it getting caught up? >> >> >> I presumed it was behind because one node was missing and this was >> blocking replication. >> >> Note the nodes are chained 1->2, 2->3, 3-4. 3 is the one that failed >> >> > > and a slonik script like > --------------- > cluster name=mycluster; > node 1 admin conninfo='...' > node 4 admin conninfo='...' > > resubscribe node(origin=1,provider=1,receiver=4); > ---------- > > is waiting? > > If so it should tell you from which node it is waiting for events from. > Close enough. I went from 2 to 4 and this is the output waiting for events (4,5002587214) only at (4,5002579907) to be confirmed on node 2 > > > > > >> >> Dave Cramer >> >> On 24 August 2015 at 15:38, Scott Marlowe >> <[email protected] <mailto:[email protected]> >> <mailto:[email protected] >> <mailto:[email protected]>>> wrote: >> >> Note that the node will still show up in sl_nodes and >> sl_status for a >> while, until slony does a cleanup event / log switch (can't >> remember >> which right now). This is normal. Don't freak out. >> >> >> >> >> >
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
