Number: 2149

Date: 11-Sep-84 16':01':05

Submitter: Le.pasa

Source: Martin Yonke

Subject: When no Leaf server found on host, don''t immediately try again

Assigned To: 

Attn: vanMelle

Status: Open

In/By: 

Problem Type: Performance

Impact: Annoying

Difficulty: Hard

Frequency: 

Priority: Unlikely

System: Communications

Subsystem: PUP Protocols

Machine: 1108

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: '
["Sannella.PA" "12-Sep-84 13':02':07" Subject': Status':(New->Open) Problem% Type':(Design% -% Impl->Performance) Impact':(->Annoying) Priority':(->Perhaps)]'
["vanMelle" "15-Sep-84 14':01':02" Subject': Attn': Difficulty':(->Hard) Priority':(Perhaps->Unlikely) Description':]

Description: Return-Path': <YONKE@USC-ECL.ARPA>'
Received': from USC-ECL.ARPA by Xerox.ARPA ; 28 AUG 84 16':43':11 PDT'
Date': Tue, 28 Aug 84 16':39':34 PDT'
From': Martin Yonke <Yonke@USC-ECL.ARPA>'
Subject': suggestion when "no leaf server" detected'
To': 1100Support.PA'
'
When a it is discovered that a host doesn''t have a leaf server, why not'
push it onto NONLEAFHOSTS so it doesn''t keep trying.'
'
Martin'
-------'
'
Date': 15 Sep 84 13':59 PDT'
From': vanMelle.pa'
Subject': Re': AR#2149': when "no leaf server" detected, should push it onto NONLEAFHOSTS'
'
Not so.  NONLEAFHOSTS is a list of hosts asserted to permanently lack a leaf server.  If Lisp fails to connect to a Leaf server on a given host, or even gets back a "no such socket" error, the condition could merely be transient, so it is correct for Lisp to try again later.'
'
One might argue that Lisp should at least wait a while before trying again, so I''ll change the ar to be that': "When no Leaf server found on host, don''t immediately try again".'
'


Workaround: 

Test Case: 

Edit-By: vanMelle

Edit-Date: 15-Sep-84 14':01':03