[Spread-users] Spread 2.5

[Ed Holyat]

John, we ran into a similar problem in our older version of spread where the token was beating the data to the next daemon and caused high retransmissions requests.  The safest fix we could think of is to resend the token back to the daemon which allowed the data to be consumed and avoid the retransmission.   This was found using multicast on VM's, but, maybe this might give insight into this issue.

-----Original Message-----
From: John Lane Schultz [mailto:jschultz at spreadconcepts.com] 
Sent: Tuesday, September 02, 2014 11:23 PM
To: Spread Users
Subject: Re: [Spread-users] Spread 2.5

>From the logs, can you tell us what state the daemons were in when this was occurring?  It could be a bug.

Cheers!

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

On Sep 2, 2014, at 10:43 PM, Yair Amir <yairamir at cs.jhu.edu> wrote:

I have a setup with 6 devices (running spread 4.4.0 on linux) with each one configured on a separate segment because they are located on separate subnets. Multicast and broadcast is not available so I configured the segments as follow
			
Spread_Segment  172.23.1.1 {
 node1   172.23.1.1
}

Spread_Segment  172.23.2.1 {
 node2   172.23.2.1
}

Spread_Segment  172.23.3.1 {
node3   172.23.3.1
}

Spread_Segment  172.23.4.1 {
 node4   172.23.4.1
}

Spread_Segment  172.23.5.1 {
 node5   172.23.5.1
}

Spread_Segment  172.23.6.1 {
 node6   172.23.6.1
}

Everything works perfectly 99.999%  of the time but it happened a few times that we had a situation where all the communication between the nodes were stalled and looking at spmonitor we discovered that some daemon were constantly retransmitting.  There was no way to get out of this mode besides restarting the daemon. During that time all communication between the nodes were work fine on all other ports (ping, 22, http, and some other udp port that we use). 

My Questions are:
- Why would that happen ?
- Is there a way to detect it and to resolve it without restarting the daemon ?

Thanks 

Claude
_______________________________________________
Spread-users mailing list
Spread-users at lists.spread.org
http://lists.spread.org/mailman/listinfo/spread-users


_______________________________________________
Spread-users mailing list
Spread-users at lists.spread.org
http://lists.spread.org/mailman/listinfo/spread-users
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: #ediff.txt
Url: http://lists.spread.org/pipermail/spread-users/attachments/20140903/0a7b74c0/attachment-0001.txt