[Spread-users] need some help diagnosing and tuning

John Schultz jschultz at spreadconcepts.com
Thu Apr 1 15:11:40 EST 2004


Mixing private ip's with public ip's usually doesn't work.

Spread expects that any daemon can communicate (route) to any other 
daemon in its configuration.  This is usually not the case with private 
ip's and multiple segments.  Apparently your configuration works 
partially, but the simplest thing to do would be to try alservice1 with 
a public ip (or remove it from the configuration) and see if that solves 
your problem.

-- 
John Lane Schultz
Spread Concepts LLC
Phn: 443 838 2200

Greg Shebert wrote:

> hi folks
> 
> i'm noticing some strange output from spmonitor for my spread network:
> 
> basically, i'm seeing some negative values for the delta parameters for
> one of my spread nodes... not sure what to make of that... also, i'm
> seeing some pretty high "Delta Mes" numbers and am wondering what i can
> do to make spread perform a bit better...
> 
> it does, occasionally, seem to get overwhelmed and reliable messages are
> being delivered but quite some time after they are handed off to a
> daemon...
> 
> thanks in advance for any guidance
> 
> 
> my config is as follows:
> 
> Spread_Segment  225.0.1.1:4803 {
>         ops1                    10.2.17.12
>         alservice1              192.92.12.51
> }
>  
> Spread_Segment  225.0.3.1:4803 {
>         adservice1              23.90.2.29
>         adservice2              23.90.2.30
> }
>  
> the node adservice2 is not yet running
> 
> spmonitor output is as follows:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Monitor> Monitor: send status query
>  
> ============================
> Status at ops1 V 3.17. 2 (state 1, gstate 1) after 514626 seconds :
> Membership  :  3  procs in 2 segments, leader is ops1
> rounds   : 2550529      tok_hurry :      37     memb change:       2
> sent pack:   93766      recv pack : 13410133    retrans    :  342010
> u retrans:  342010      s retrans :       0     b retrans  :       0
> My_aru   : 70120046     Aru       : 70120003    Highest seq: 70120046
> Sessions :      21      Groups    :      20     Window     :      60
> Deliver M: 70153248     Deliver Pk: 70155564    Pers Window:      15
> Delta Mes:   37087      Delta Pack:    1650     Delta sec  :     356
> ==================================
>  
> Monitor>
> ============================
> Status at alservice1 V 3.17. 2 (state 1, gstate 1) after 514713 seconds
> :
> Membership  :  3  procs in 2 segments, leader is ops1
> rounds   : 2555114      tok_hurry :     189     memb change:       3
> sent pack: 10393955     recv pack : 4198819     retrans    :   11366
> u retrans:   11284      s retrans :       0     b retrans  :      82
> My_aru   : 70120046     Aru       : 70120027    Highest seq: 70120046
> Sessions :     377      Groups    :      20     Window     :      60
> Deliver M: 70165696     Deliver Pk: 70168249    Pers Window:      15
> Delta Mes:   12448      Delta Pack:      24     Delta sec  :      87
> ==================================
>  
> Monitor>
> ============================
> Status at adservice1 V 3.17. 2 (state 1, gstate 1) after 514280 seconds
> :
> Membership  :  3  procs in 2 segments, leader is ops1
> rounds   : 2533438      tok_hurry :       5     memb change:       1
> sent pack: 2909774      recv pack : 10807939    retrans    : 1193177
> u retrans: 1093291      s retrans :   99879     b retrans  :       7
> My_aru   : 70120051     Aru       : 70120036    Highest seq: 70120051
> Sessions :      76      Groups    :      20     Window     :      60
> Deliver M: 70117796     Deliver Pk: 70120051    Pers Window:      15
> Delta Mes:  -47900      Delta Pack:       9     Delta sec  :    -433
> ==================================
> 
> 
> 
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
> 







More information about the Spread-users mailing list