Re: Cluster XL - Old or too-new arriving updates Are the two systems physically seperated? I had to adjust the Timers by 10 (we run a ClusterXL cluster across a WAN) regards Martijn lawrencium(root)# cphaprob syncstat Sync Statistics (IDs of F&A Peers - 1 ): Other Member Updates: Sent retransmission requests................... 0 Avg missing updates per request................ 0 Old or too-new arriving updates................ 0 Unsynced missing updates....................... 0 Lost sync connection (num of events)........... 1 Timed out sync connection ..................... 2 Local Updates: Total generated updates ....................... 2161345 Recv Retransmission requests................... 92 Recv Duplicate Retrans request................. 1 Blocking Events................................ 0 Blocked packets................................ 0 Max length of sending queue.................... 0 Avg length of sending queue.................... 0 Hold Pkts events............................... 1584 Unhold Pkt events.............................. 1584 Not held due to no members..................... 66 Max held duration (sync ticks)................. 11 Avg held duration (sync ticks)................. 0 Timers: Sync tick (ms)................................. 100 CPHA tick (ms)................................. 1000 Queues: Sending queue size............................. 512 Receiving queue size........................... 256 |