Return-Path: william@bourbon.usc.edu Delivery-Date: Thu Oct 9 19:57:57 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 m9A2vvnZ011492 for ; Thu, 9 Oct 2008 19:57:57 -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 m9A34ZeZ017122 for ; Thu, 9 Oct 2008 20:04:35 -0700 Message-Id: <200810100304.m9A34ZeZ017122@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Beacon Node fully connected mesh Date: Thu, 09 Oct 2008 20:04:35 -0700 From: Bill Cheng Someone wrote: > How long should a Beacon node keep trying to connect to other beacon nodes. Forever! > Say for example... In a start up config file there are 5 beacon nodes (I m > the 1st in the List). > Now I should try to connect to other 4 Beacon Nodes. > Suppose out of [BeaconNode 2. BeaconNode 3. BeaconNode 4 and BeaconNode 5], > BeaconNode 2 and BeaconNode 5 are *not Up*. > So I should, in this case, Wait for Retry Time and try again Yep! > But what should I do after I 'm fully connected to all Beacon Nodes? Then there is no need to have the retry timer going (conceptually). If a beacon node goes down, you need to restart the retry timer. -- Bill Cheng // bill.cheng@usc.edu