[Spread-users] Membership changes

[Dean Bennett]

I am seeing a membership change in spmonitor every 90 seconds..  Any 
ideas as to what could cause that?

Network config is 9 hosts, all but one with 2 network interfaces.  We 
tried the multi-homed setup in spread.conf, but it never worked well, so 
we ended up with multiple segments.  Everything is working but spmonitor 
shows a lot of membership changes.  Here is the log with just the 4 
hosts on the local network up:


[Thu 16 Mar 2006 17:25:48] Memb_handle_message: handling join message 
from -945381375, State is 1
[Thu 16 Mar 2006 17:25:48] Handle_join in OP
[Thu 16 Mar 2006 17:25:48] Memb_token_loss: I lost my token, state is 1
[Thu 16 Mar 2006 17:25:48] Scast_alive: State is 2
[Thu 16 Mar 2006 17:25:48] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:48] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:48] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:48] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:48] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:48] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:50] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:50] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:50] Scast_alive: State is 2
[Thu 16 Mar 2006 17:25:50] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:50] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:50] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:50] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:52] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:52] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:52] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:52] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:52] Scast_alive: State is 2
[Thu 16 Mar 2006 17:25:52] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:52] Handle_alive in SEG
[Thu 16 Mar 2006 17:25:53] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:25:53] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:25:53] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:53] Handle_alive in REPRESENTED
[Thu 16 Mar 2006 17:25:55] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:25:55] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:25:55] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:55] Handle_alive in REPRESENTED
[Thu 16 Mar 2006 17:25:57] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:25:57] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:25:57] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:57] Handle_alive in REPRESENTED
[Thu 16 Mar 2006 17:25:59] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:25:59] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:25:59] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:25:59] Handle_alive in REPRESENTED
[Thu 16 Mar 2006 17:26:01] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:26:01] Memb_handle_message: handling alive message
[Thu 16 Mar 2006 17:26:01] Handle_alive in REPRESENTED
[Thu 16 Mar 2006 17:26:01] Memb_handle_message: handling join message 
from -945381375, State is 3
[Thu 16 Mar 2006 17:26:03] Memb_handle_token: handling form1 token
[Thu 16 Mar 2006 17:26:03] Handle_form1 in REPRESENTED
[Thu 16 Mar 2006 17:26:03] Memb_handle_token: handling form1 token
[Thu 16 Mar 2006 17:26:03] Handle_form1 in FORM
[Thu 16 Mar 2006 17:26:03] Memb_handle_token: handling form2 token
[Thu 16 Mar 2006 17:26:03] Handle_form2 in FORM
[Thu 16 Mar 2006 17:26:03] Memb_handle_token: handling form2 token
[Thu 16 Mar 2006 17:26:03] Handle_form2 in EVS
[Thu 16 Mar 2006 17:26:03] Memb_transitional
[Thu 16 Mar 2006 17:26:03] Memb_regular
Membership id is ( -945381375, 1142555164)
[Thu 16 Mar 2006 17:26:03] --------------------
[Thu 16 Mar 2006 17:26:03] Configuration at HOST2B is:
[Thu 16 Mar 2006 17:26:03] Num Segments 7
[Thu 16 Mar 2006 17:26:03]      2       199.166.160.255   4813
[Thu 16 Mar 2006 17:26:03]              HOST1A                 199.166.160.1
[Thu 16 Mar 2006 17:26:03]              HOST3A                 199.166.160.3
[Thu 16 Mar 2006 17:26:03]      2       199.166.161.255   4813
[Thu 16 Mar 2006 17:26:03]              HOST2B                 199.166.161.2
[Thu 16 Mar 2006 17:26:03]              HOST4B                 199.166.161.4
[Thu 16 Mar 2006 17:26:03]      0       199.166.162.255   4813
[Thu 16 Mar 2006 17:26:03]      0       199.166.163.255   4813
[Thu 16 Mar 2006 17:26:03]      0       10.16.44.255      4813
[Thu 16 Mar 2006 17:26:03]      0       10.16.45.255      4813
[Thu 16 Mar 2006 17:26:03]      0       172.25.16.255     4813
[Thu 16 Mar 2006 17:26:03] ====================

The next set of membership messages always start exactly 90 seconds 
after the 'Configuration at' message.

I 've tried adjusting the Wide_network timeouts in membership.c up, and 
disabling the Wide_network config as per a previous post.
HOST1-4 are on a local network, HOST5,6&9 are over a WAN, and HOST7&8 go 
through a router.

Spread_Segment  199.166.160.255:4813 {
        HOST1A  199.166.160.1
        HOST2A 199.166.160.2
        HOST3A 199.166.160.3
        HOST4A 199.166.160.4
}

Spread_Segment  199.166.161.255:4813 {
        HOST1B  199.166.161.1
        HOST2B   199.166.161.2
        HOST3B  199.166.161.3
        HOST4B   199.166.161.4
}

Spread_Segment  199.166.162.255:4813 {
        HOST5A   199.166.162.1
        HOST6A  199.166.162.3
}

Spread_Segment  199.166.163.255:4813 {
        HOST5B  199.166.163.1
        HOST6B   199.166.163.3
}

Spread_Segment  10.16.44.255:4813 {
        HOST7A   10.16.44.100
        HOST8A   10.16.44.101
 }

Spread_Segment  10.16.45.255:4813 {
        HOST7B  10.16.45.100
        HOST8B  10.16.45.101
}

Spread_Segment  172.25.16.255:4813 {
        HOST9   172.25.16.63
}