Thu Feb 28 01:19:21 PST 2008
- Previous message: [Slony1-general] failover problems with 3 nodes
- Next message: [Slony1-general] Slony locks tables that are not even in replication sets?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi > > > [...] > > Hey, I should test failover before updating to 1.2.13... > > I have some strange periodic problems with 'ACCEPT_SET - MOVE_SET or > FAILOVER_SET not received yet - sleep' on 1.2.12 and 1.2.13. Looks > similar to this one. I tried 'move set' on 1.2.13 and 'ACCEPT_SET - MOVE_SET or FAILOVER_SET not received yet - sleep' occurred on node 3. I could update the tupples on node 2 and get new data on node 1, but node 3 was never updated. I tried several times. The problem didn't always but sometimes happened. execute command: lock set (id =1, origin =1); wait for event (origin = 1, confirmed = 2); move set (id=1, old origin = 1, new origin=2); > > I should try to downgrade to 1.2.11 and try if my 'move set' problems > will disappear. Here is the initial problem description: > http://lists.slony.info/pipermail/slony1-general/2008-February/007445.html > > -- > Mikhail Kolesnik > ICQ: 260259143 > IRC: mike_k at freenode/#crux, rusnet/#yalta > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > -- SRA OSS, Inc. 日本支社 Yoshiharu Mori <y-mori at sraoss.co.jp> http://www.sraoss.co.jp/
- Previous message: [Slony1-general] failover problems with 3 nodes
- Next message: [Slony1-general] Slony locks tables that are not even in replication sets?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list