<span class="gmail_quote"></span><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><span class="q" id="q_11494cf621333bea_0"><span class="gmail_quote">
</span><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks for the information. <br>I tried a few more things and I think the reason I was seeing the unexpected behaviour could be that the machines were seeing a pretty high load could have led to the token passing taking more time than expected.
<br>Could this be the cause of the frequent partitions and then the re-merges?<br>I also saw that the Spread guide recommends running Spread with a higher priority so I'll be trying that to see if it solves the problem.
<br><br>Thanks,<br><span>Uma</span><div><span><br><br><br><div><span class="gmail_quote">On 8/23/07, <b class="gmail_sendername">Yair Amir</b> <<a href="mailto:yairamir@jhu.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
yairamir@jhu.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I'll add that Spread provides detailed information in the membership<br>messages. If you have real group members (as opposed to the printout<br>of the daemon) and you are careful to analyze the membership events,
<br>the who-came-with-whom components included in them, and the transitional signals,<br>it will give you the complete picture.<br><br>Cheers,<br><br> :) Yair.<br><br>John Schultz wrote:<br>> This behavior can happen. The token is being lost in your network for
<br>> some reason. This causes the 2nd daemon to try and form its own<br>> membership, which it succeeds in doing. The 1st daemon has not yet<br>> finished forming its own membership when it gets probed or it probes the
<br>> other daemon and they rejoin together.<br>><br>> The very fact that the first daemon had to install another membership<br>> indicates that the second daemon parititoned away and then came back to<br>> it (quickly).
<br>><br>> Cheers!<br>><br>> ---<br>> John Schultz<br>> Spread Concepts<br>> Phn: 443 838 2200<br>><br>> On Thu, 23 Aug 2007, Uma Chingunde wrote:<br>><br>>> I am sorry about the spam if this email has been seen multiple times.
<br>>> Resending without the log files.<br>>><br>>> On 8/22/07, Uma Chingunde <<a href="mailto:umac@jhu.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">umac@jhu.edu</a>> wrote:
<br>>>><br>>>> Hi,<br>>>><br>>>> I have a Spread configuration between 2 hosts and I am seeing some weird
<br>>>> behavior between them.<br>>>> Since the network does not support broadcast I have configured both<br>>>> hosts<br>>>> as separate sites.<br>>>><br>>>> My spread.conf
looks like this:<br>>>> --------<br>>>> Spread_Segment x.x.x.255:4899 {<br>>>><br>>>> uma-vm-1 x.x.x.105<br>>>> }<br>>>> Spread_Segment x.x.x.255
:4899 {<br>>>><br>>>> uma-vm-2 x.x.x.106<br>>>> }<br>>>> ---------------------<br>>>><br>>>> I have a test application that communicates using spread.
<br>>>> However at certain intervals the second daemon seems to partition<br>>>> away and<br>>>> then re-merge when no network change has occurred.<br>>>> I initially thought that the application was sending a wrong message to
<br>>>> spread that was causing the problem. However it doesn't seem to be<br>>>> the case.<br>>>><br>>>><br>>>> The first daemon's log file (spread1.log) shows both daemons as always
<br>>>> being in the same partition.<br>>>> The log files for the partitioned daemon (spread2.log) shows the<br>>>> segments<br>>>> occasionally in different partitions.<br>>>>
<br>>>> The relevant snippets are below and the log files are attached.<br>>>> Does anyone have an idea about why I am seeing such behavior?<br>>>> I can't figure out why one daemon would see a network partition
<br>>>> differently from the other, if such a partition was occurring which I am<br>>>> pretty sure in this case is not.<br>>>> Is there a configuration issue that I am missing somewhere?<br>>>>
<br>>>> Any help would be appreciated.<br>>>> Thanks,<br>>>> Uma<br>>>><br>>>> Log file snippet for first daemon<br>>>> ------------------------------------------<br>
>>> Conf_load_conf_file: My name: uma-vm-1, id:
x.x.x.105, port: 4899<br>>>> Membership id is ( 168918633, 1187811520)<br>>>> --------------------<br>>>> Configuration at uma-vm-1 is:<br>>>> Num Segments 2<br>>>> 1 x.x.x.255
4899<br>>>> uma-vm-1 x.x.x.105<br>>>> 1 x.x.x.255 4899<br>>>> uma-vm-2 x.x.x.106<br>>>> ====================<br>>>> Membership id is ( 168918633, 1187811620)
<br>>>> --------------------<br>>>> Configuration at uma-vm-1 is:<br>>>> Num Segments 2<br>>>> 1 x.x.x.255 4899<br>>>> uma-vm-1 x.x.x.105<br>
>>> 1
x.x.x.255 4899<br>>>> uma-vm-2 x.x.x.106<br>>>> ====================<br>>>> Membership id is ( 168918633, 1187811682)<br>>>> --------------------<br>>>> Configuration at uma-vm-1 is:
<br>>>> Num Segments 2<br>>>> 1 x.x.x.255 4899<br>>>> uma-vm-1 x.x.x.105<br>>>> 1 x.x.x.255 4899<br>>>> uma-vm-2
x.x.x.106<br>>>> ====================<br>>>> Membership id is ( 168918633, 1187811800)<br>>>> --------------------<br>>>><br>>>> Log file snippet for second daemon<br>>>> ---------------------------------------
<br>>>> Membership id is ( 168918633, 1187811520)<br>>>> --------------------<br>>>> Configuration at uma-vm-2 is:<br>>>> Num Segments 2<br>>>> 1 x.x.x.255 4899<br>
>>> uma-vm-1
x.x.x.105<br>>>> 1 x.x.x.255 4899<br>>>> uma-vm-2 x.x.x.106<br>>>> ====================<br>>>> Membership id is ( 168918633, 1187811620)<br>>>> --------------------
<br>>>> Configuration at uma-vm-2 is:<br>>>> Num Segments 2<br>>>> 1 x.x.x.255 4899<br>>>> uma-vm-1 x.x.x.105<br>>>> 1 x.x.x.255 4899
<br>>>> uma-vm-2 x.x.x.106<br>>>> ====================<br>>>> Membership id is ( 168918634, 1187811665)<br>>>> --------------------<br>>>> Configuration at uma-vm-2 is:
<br>>>> Num Segments 2<br>>>> 0 x.x.x.255 4899<br>>>> 1 x.x.x.255 4899<br>>>> uma-vm-2 x.x.x.106<br>>>> ====================<br>>>> Membership id is ( 168918633, 1187811682)
<br>>>> --------------------<br>>>> Configuration at uma-vm-2 is:<br>>>> Num Segments 2<br>>>> 1 x.x.x.255 4899<br>>>> uma-vm-1 x.x.x.105<br>
>>> 1
x.x.x.255 4899<br>>>> uma-vm-2 x.x.x.106<br>>>> ====================<br>>>><br>>>><br>>><br>><br>> _______________________________________________
<br>> Spread-users mailing list<br>> <a href="mailto:Spread-users@lists.spread.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Spread-users@lists.spread.org</a><br>> <a href="http://lists.spread.org/mailman/listinfo/spread-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.spread.org/mailman/listinfo/spread-users
</a><br>><br>><br><br><br>_______________________________________________<br>Spread-users mailing list<br><a href="mailto:Spread-users@lists.spread.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Spread-users@lists.spread.org</a><br><a href="http://lists.spread.org/mailman/listinfo/spread-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.spread.org/mailman/listinfo/spread-users</a><br></blockquote></div><br>
</span></div></blockquote></div><br>
</span></div></blockquote></div><br>