View Single Post
  #1 (permalink)  
Old 2006-06-15
kraemer kraemer is offline
Junior Member
 
Join Date: 2005-10-26
Posts: 4
Rep Power: 0
kraemer has an average reputation (10+)
Send a message via ICQ to kraemer
Default Cluster XL - Old or too-new arriving updates

Hi CP-Gurus!
I have some questions to the output of cphaprob syncstat command
on an SPLAT R60 HFA3 Cluster XL:

The output on my platform looks like this:

cphaprob syncstat

Sync Statistics (IDs of F&A Peers - 1 ):

Other Member Updates:
Sent retransmission requests................... 256
Avg missing updates per request................ 1
Old or too-new arriving updates................ 78804199
Unsynced missing updates....................... 0
Lost sync connection (num of events)........... 29
Timed out sync connection ..................... 0

Local Updates:
Total generated updates ....................... 7832822
Recv Retransmission requests................... 124
Recv Duplicate Retrans request................. 138

Blocking Events................................ 0
Blocked packets................................ 0
Max length of sending queue.................... 0
Avg length of sending queue.................... 0
Hold Pkts events............................... 10703181
Unhold Pkt events.............................. 10703181
Not held due to no members..................... 13
Max held duration (sync ticks)................. 1
Avg held duration (sync ticks)................. 0

Timers:
Sync tick (ms)................................. 100
CPHA tick (ms)................................. 100

Queues:
Sending queue size............................. 512
Receiving queue size........................... 256

My general question is aboute the value of:
Old or too-new arriving updates................

In the Cluster XL guide is an hint about the value, that says:
"a large value implys connectivity problems"
But I can't find anything until now in our network.

The next tips are: enlarge the reciving queue or contact the Technical Support ...

Are there any experiences on your side with this problems. Can anyone give some reference values for the reciving queue, perhaps in dependency of the traffic going through an Cluster.
(Our cluster is running in pivot mode)

I am thankful for any suggestions or tips..

Regards
Karsten
Reply With Quote