[28467] in Kerberos
Re: MIT Incremental Propagation
daemon@ATHENA.MIT.EDU (John Hascall)
Fri Sep 21 23:32:28 2007
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
In-reply-to: Your message of Fri, 21 Sep 2007 20:49:05 -0400.
<200709220049.l8M0n6hR028443@ginger.cmf.nrl.navy.mil>
Date: Fri, 21 Sep 2007 22:31:50 CDT
Message-ID: <29490.1190431910@malison.ait.iastate.edu>
From: John Hascall <john@iastate.edu>
Cc: kerberos@mit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
> >Ubik is an elected-master protocol. All updates go to the master
> >which replicates. If the master goes away, after a while the
> >remaining nodes notice and revote a new master (this can take a while).
> >
> >I'm not sure that model works well with the KDC's single-threadedness.
> >
> >I expect a 3-phase commit model would be more robust.
>
> I think you're conflating the master election protocol with the
> transaction protocol. You still need to decide on a master (aka
> "coordinator") with 2PC or 3PC.
You do not. Each transaction can be mastered by whichever
node it starts out on. As soon as it has >50% acks to the
prepare, it can issue the commits. At the same time another
node can be mastering a different transaction.
John
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
