[Spread-users] Token circulates very frequently
Stanisław Trytek
tryteks at pit.edu.pl
Fri Jul 7 05:58:41 EDT 2006
I am noticing some strange behaviour with the token from time to time.
Even if nothing is being sent the regular token circulates very frequently
in one segment.
It seems that the token is not swallowed by leader after a round.
Take a look at monitor output: 80rounds per second.
I happens in version 4.0.0 as well as in 3.17.3;
In that case that behavior was triggered by regular membership message but
it is not rule.
That strange state is difficult to trigger but I am trying to figure out
what is the cause of that.
Does sombody experienced such spread's behaviour?
Stanislaw Trytek
Monitor> Monitor: send status query
============================
Status at node0070 V 4.00. 0 (state 1, gstate 1) after 1037 seconds :
Membership : 3 procs in 1 segments, leader is node0070
rounds : 337 tok_hurry : 167 memb change: 3
sent pack: 10 recv pack : 2 retrans : 0
u retrans: 0 s retrans : 0 b retrans : 0
My_aru : 12 Aru : 12 Highest seq: 13
Sessions : 1 Groups : 1 Window : 50
Deliver M: 11 Deliver Pk: 20 Pers Window: 10
Delta Mes: 0 Delta Pack: 0 Delta sec : 37
==================================
Monitor>
============================
Status at node0063 V 4.00. 0 (state 1, gstate 1) after 180 seconds :
Membership : 3 procs in 1 segments, leader is node0070
rounds : 152 tok_hurry : 25 memb change: 1
sent pack: 1 recv pack : 3 retrans : 0
u retrans: 0 s retrans : 0 b retrans : 0
My_aru : 12 Aru : 12 Highest seq: 13
Sessions : 0 Groups : 1 Window : 50
Deliver M: 10 Deliver Pk: 12 Pers Window: 10
Delta Mes: -1 Delta Pack: 0 Delta sec : -857
==================================
Monitor>
============================
Status at lap0001 V 4.00. 0 (state 1, gstate 1) after 1010 seconds :
Membership : 3 procs in 1 segments, leader is node0070
rounds : 327 tok_hurry : 163 memb change: 2
sent pack: 2 recv pack : 11 retrans : 0
u retrans: 0 s retrans : 0 b retrans : 0
My_aru : 13 Aru : 12 Highest seq: 13
Sessions : 1 Groups : 1 Window : 50
Deliver M: 11 Deliver Pk: 21 Pers Window: 10
Delta Mes: 1 Delta Pack: 0 Delta sec : 830
==================================
Monitor> Monitor: send status query
============================
Status at node0070 V 4.00. 0 (state 1, gstate 1) after 1047 seconds :
Membership : 3 procs in 1 segments, leader is node0070
rounds : 417 tok_hurry : 167 memb change: 3
sent pack: 10 recv pack : 2 retrans : 0
u retrans: 0 s retrans : 0 b retrans : 0
My_aru : 12 Aru : 12 Highest seq: 13
Sessions : 1 Groups : 1 Window : 50
Deliver M: 11 Deliver Pk: 20 Pers Window: 10
Delta Mes: 0 Delta Pack: 0 Delta sec : 37
==================================
Monitor>
============================
Status at node0063 V 4.00. 0 (state 1, gstate 1) after 190 seconds :
Membership : 3 procs in 1 segments, leader is node0070
rounds : 232 tok_hurry : 25 memb change: 1
sent pack: 1 recv pack : 3 retrans : 0
u retrans: 0 s retrans : 0 b retrans : 0
My_aru : 12 Aru : 12 Highest seq: 13
Sessions : 0 Groups : 1 Window : 50
Deliver M: 10 Deliver Pk: 12 Pers Window: 10
Delta Mes: -1 Delta Pack: 0 Delta sec : -857
==================================
Monitor>
============================
Status at lap0001 V 4.00. 0 (state 1, gstate 1) after 1020 seconds :
Membership : 3 procs in 1 segments, leader is node0070
rounds : 407 tok_hurry : 163 memb change: 2
sent pack: 2 recv pack : 11 retrans : 0
u retrans: 0 s retrans : 0 b retrans : 0
My_aru : 13 Aru : 12 Highest seq: 13
Sessions : 1 Groups : 1 Window : 50
Deliver M: 11 Deliver Pk: 21 Pers Window: 10
Delta Mes: 1 Delta Pack: 0 Delta sec : 830
==================================
More information about the Spread-users
mailing list