[OpenAFS] openafs high availability problem

[Derrick J Brashear]

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-1328366167-1188422038=:11165
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by meredith.dementia.org id l7TLDxWe027813

On Wed, 29 Aug 2007, sophana wrote:

> Derrick Brashear a =E9crit :
>>=20
>>
>>     I would be interrested in this patch. Thanks
>>
>>     Isnt'it possible to add this feature as an option? (or at least a
>>     compilation option)
>>=20
>>=20
>> Probably
>>
>>     1 minute is really too long for a filesystem. Any user would say i=
t is
>>     no more working.
>>=20
>>=20
>> 5 seconds is so short that on a WAN if you need to retransmit a single=
 time=20
>> (it's udp, remember) you're screwed.
>>=20
> So short?
> Do you know anyone waiting more than 5 seconds the file that he opened?

I wonder if I know myself. I'll check.

Yup.

>> Not all uses of AFS will be local.
>
> Even on remote, 5 seconds is a lot.
> The algorithm has to be re-thinked.

Um, you gonna buy me a faster cellphone data network?

Seriously.

I still have ping times with 35 second latency in an xterm here.

Yes, I use AFS from "the field". And it works. But not in 5 seconds.



---559023410-1328366167-1188422038=:11165--