Return-Path: william@bourbon.usc.edu
Delivery-Date: Mon Oct 27 19:22:54 2008
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.3
Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75])
	by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m9S2MsSn027826
	for <cs551@merlot.usc.edu>; Mon, 27 Oct 2008 19:22:54 -0700
Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1])
	by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m9S2XsLL019825
	for <cs551@merlot>; Mon, 27 Oct 2008 19:33:54 -0700
Message-Id: <200810280233.m9S2XsLL019825@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: not enough neighbors after soft restart
Date: Mon, 27 Oct 2008 19:33:54 -0700
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > I meant that :
  > After reception of join responses (in any case), the node connects to 
  > init neighbors and add them into the file.

It doesn't work this way!  After you get join responses, you
wait for JoinTimeout (or <Cntrl+C>), then you disconnect from
the beacon node, create the init_neighbor_list file, and do
a soft restart.

  > I want to know that if the responses returned are less than both init 
  > and min neighbors, then should it do a soft restart or die out ?

You need to ignore MinNeighbors at this point because you
are still in the JOIN phase!  The only thing that matters
during the JOIN phase is InitNeighbors.  Please read the
part of the spec that explains these values again.

If you cannot get more than or equal to InitNeighbors
number of JOIN responses during JOIN, please see:

    http://merlot.usc.edu/cs551-f08/projects/final-faq.html#no-enough-join
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>




  Bill Cheng wrote:
  > Someone wrote:
  >
  >   > So, then in case of join, spec says the node should "rejoin" the network 
  >   > (based on the init neighbors). So, should it soft start or die out in 
  >   > this case ?
  >   > Because, if it soft starts, then it could be softstarting for ever.
  >
  > I'm not sure what you are referring to.  Everywhere in the spec
  > where it says "rejoin the network", it always say delete
  > init_neighbor_list first!  So, it cannot do a "rejoin based
  > on the init neighbors".
  >
  > A regular node is either JOINing the network (when it does
  > not have an init_neighbor_list file) or participating in the
  > network (when it has an init_neighbor_list file).  It cannot
  > do both.
  > --
  > Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>
  >
  >
  >
  >
  >   > Someone wrote:
  >   >
  >   >   > If the no of neighbors up are less than the min. neighbors then a node
  >   >   > does soft restart.
  >   >
  >   > And delete init_neighbor_list file.
  >   >
  >   >   > what if , even after soft restart , the number of neighbors up are
  >   >   > less than min_neighbors, then what a node should do ?
  >   >
  >   > When it restarts, it's doing a JOIN, so it ignores MinNeighbors.
  >   > During the JOIN, what matters is InitNeighbors.
  >   >
  >   >   > Exit or try to send join requests continuously till it finds the
  >   >   > enough number of neighbors ?
  >   >
  >   > This JOIN is no different than other JOINs!
  >   > --
  >   > Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>