[2172] in SIPB-AFS-requests
Re: [daemon@MIT.EDU : quorum? (was Re: Intermediate Caching)]
daemon@ATHENA.MIT.EDU (Richard Basch)
Thu Oct 26 18:57:23 1995
Date: Thu, 26 Oct 1995 18:51:46 -0400
To: jweiss@MIT.EDU
Cc: afsdev@MIT.EDU, sipb-afsreq@MIT.EDU
In-Reply-To: <199510262153.RAA03954@the-other-woman.MIT.EDU>
From: "Richard Basch" <basch@lehman.com>
Your statement is accurate... prdb still requires quorum until 3.4. You
may want to investigate the feasibility of relaxing this restriction in
the 3.3 code, as I don't think the code changes would be too
substantial.
-Richard
On Thu, 26-October-1995, "jweiss@mit.edu" wrote to "afsdev@MIT.EDU, sipb-afsreq@MIT.EDU" saying:
>
> Assuming this (that 3.4 servers will give out prdb info w/o a sync
> site) is true, it means that running 3.4 on our servers (once it is
> stable, of course) might make two DB server cells less dangerous.
>
> Jonathon
>
>
> ------- Forwarded transaction
>
> [4190] daemon@ATHENA.MIT.EDU (srivas@transarc.com) Info-AFS_Redistribution 10/25/95 16:32 (15 lines)
> Subject: quorum? (was Re: Intermediate Caching)
> Date: Wed, 25 Oct 1995 14:39:02 EDT
> From: srivas@transarc.com
> To: rens@imsi.com
> Cc: Info-AFS@transarc.com, bb+transarc.clippings@transarc.com
>
> >Can't do this until servers can continue to serve Read-Only volumes
> >while partitioned from quorum. Waiting..... :)
>
> *File* servers never have participated in any kind of quorum stuff.
>
> Database servers do, but they don't serve volumes. FWIW, the pts and
> kas database servers do give out read-only info even when not in quorum
> (pts added in 3.4). The volume-location database servers will still not
> give out r/o data out of quorum.
>
> --[4190]--
>
> ------- End forwarded transaction
--
Richard Basch
Lehman Brothers, Inc. Email: basch@lehman.com
101 Hudson Street 33rd Flr. Fax: +1-201-524-5828
Jersey City, NJ 07302 Voice: +1-201-524-5049
