[Spread-users] Re: Spread-users digest, Vol 1 #522 - 2 msgs

[Tom Mornini]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Apr 15, 2004, at 9:00 AM, spread-users-request at lists.spread.org 
wrote:

>    2. "Spread hanging in logging application" redux? (Jack Repenning)
>

> Message: 2
> To: spread-users at lists.spread.org
> From: Jack Repenning <jrepenning at collab.net>
> Date: Wed, 14 Apr 2004 17:58:31 -0700
> Subject: [Spread-users] "Spread hanging in logging application" redux?
>
> Just about two years ago:
>
> http://lists.spread.org/pipermail/spread-users/2002-April/000705.html
>
> ... there was a discussion in this list about a Spread hang that could
> arise under certain conditions of membership or network instability.
> At that time, Yair seemed to be on the trail of an enhancement to
> repair communications after such an event, but didn't think it
> appropriate to include in the then-current release (3.16.2).  Something
> about "to have on the token another field that will report the id of
> the daemon that set the ARU and caused it to go down."  Did such a
> change make it into 3.17?  I grubbed the release notes and other email
> archives assiduously, but couldn't confirm (or deny) it.
>
> Reason I ask: one of our sites just ran into something (once,
> non-reproducible at this point) that looks rather same-ish, running
> Spread 3.17.1.  If the fix actually did make it into 3.17, then I'm
> obviously smokin' something.  If it didn't ... can I help it along?

I tried to verify the fix, but was never able to convince my 
organization to
trust Spread enough to place it back into production, or devote the 
resources
to test it fully after several days in hell due that described bug.

- -- 
- -- Tom Mornini
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFAftb4zaKkuvKwKvcRAqPDAJ9E/y+l8ALL7apwv4BEuu3fLl/+AQCfdIjV
Pz3XwkWQjtdAA1J3Rks8BAE=
=3Eri
-----END PGP SIGNATURE-----