Return-Path: william@bourbon.usc.edu Delivery-Date: Mon Oct 6 21:31:21 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 m974VKIM031534 for ; Mon, 6 Oct 2008 21:31:20 -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 m974bGXQ001344 for ; Mon, 6 Oct 2008 21:37:16 -0700 Message-Id: <200810070437.m974bGXQ001344@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Non-beacon node Date: Mon, 06 Oct 2008 21:37:16 -0700 From: Bill Cheng Someone wrote: > When a non-beacon node comes up, it tries to "connect" to one of the > beacon nodes, if it can't it doesn't retry; it tries the next beacon > node. > What if it can't connect to any of the beacon nodes ? > Does it print an error message and exit OR does it go to sleep and retry again ? There is no retrying for a non-beacon node. If a regular node is trying to join and cannot find a beacon node who's up, it should just die with an error message. -- Bill Cheng // bill.cheng@usc.edu