X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B431.2F26ABC6@onstor-exch02.onstor.net>; Thu, 21 Jun 2007 10:22:54 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: PERFORCE change 24319 for review
Date: Thu, 21 Jun 2007 10:22:54 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E038F8E0C@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0443A1DC@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PERFORCE change 24319 for review
Thread-Index: Ace0GDJzeCMhwbYITvyFd8ddnRD8HgAEWs3QAAGcpKA=
From: "James Kahn" <james.kahn@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
Cc: "dl-Software" <dl-software@onstor.com>

RMC session timeout is set to 124 seconds.  SPM arbitrarily sets
internal
Timeout to 20 seconds.  Technically, the second (lower) timeout is
unnecessary with rmc.  But, it's a hold-over for sendAgile.

The failure occurs during an RPC msg which includes processing time of
The endpoint too unlike asynch messages which do not.

Complete conversion to RMC would eliminate this interim timeout issue
As SPM would then depend wholely on the RMC session timeout. =20

This is sufficient for super soak until the bigger issue can be dealt
with.

-Jim


-----Original Message-----
From: Maxim Kozlovsky=20
Sent: Thursday, June 21, 2007 10:36 AM
To: James Kahn
Cc: dl-Software
Subject: RE: PERFORCE change 24319 for review

Jim (and everybody else),

If you are modifying a timeout value, you need to provide some
explanation how you have arrived to this particular timeout value, why
the new timeout value is sufficient, what variables this timeout value
depends on. "This test did not pass with old value, it passes with new"
does not mean that the problem is fixed.

Max

-----Original Message-----
From: James Kahn=20
Sent: Thursday, June 21, 2007 8:24 AM
To: Andy Sharp; Brian DeForest; Charissa Willard; Chris Vandever;
Danqing Jin; Henry Lau; Ian Brown; Jobi Ariyamannil; Jonathan Goldick;
Ken Renshaw; Larry Scheer; Maxim Kozlovsky; Mike Lee; Sandrine
Boulanger; Tim Gardner
Subject: PERFORCE change 24319 for review

Change 24319 by jamesk@jamesk-work3.1 on 2007/06/21 08:19:14

	Fix for TED19431, spm not registering luns in large
configurations due to premature
	timeout.  Increased spm cluster lun probe timeout to 60 seconds
from 20 seconds.
	   Increased spm base poll rate to once every 5 seconds to
reduce traffic.
	Reviewed by rendellf.

Affected files ...

... //depot/ZONDA/nfx-tree/code/sm-spm/spm-poll.c#3 edit
... //depot/ZONDA/nfx-tree/code/sm-spm/spm.h#3 edit


http://liszt:1818/@md=3Dd&cd=3D//depot/$c=3DG35@//24319?ac=3D10
