Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Oct 26 22:09:01 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 m9R591L1014057 for ; Sun, 26 Oct 2008 22:09:01 -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 m9R5JmoC027093 for ; Sun, 26 Oct 2008 22:19:48 -0700 Message-Id: <200810270519.m9R5JmoC027093@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Final Proj Part 1 (Doubt with join timeout) Date: Sun, 26 Oct 2008 22:19:48 -0700 From: Bill Cheng Someone wrote: > I have a doubt with the join timeout. Suppose I receive a join response > from a node, I wait for join timeout to get over before trying to > connect to the node. > What if one of the nodes has shut down the connection already? What > should be my system's behavior in this case? Remember, when you do a soft-restart, it's as if you shutdown your node and start it again. Anything can happen between the time you shutdown your node and start it again and you need to be ready to deal with it. In this case, it's just like when you start this node, it cannot connect to MinNeighbor number of nodes. You should delete init_neighbor_list file and do a soft-restart. -- Bill Cheng // bill.cheng@usc.edu