Well, you guys let me know if I can help you in any way. > I think there is a time and place for this and can be leveraged in other > protocols. As a minimum it can be a pluggable protocol. Its a great > start. > > [EMAIL PROTECTED] wrote: >>> Given the inherent over head in total order protocols, I think we >>> should work to limit the messages passed over the protocol, to only >>> the absolute minimum to make our cluster work reliably. >>> Specifically, I think this is only the distributed lock. For state >>> replication we can use a much more efficient tcp or udp based protocol. >> >> As I said, if your workload has low data sharing (e.g. session >> replication), you should not use totem. It's designed for systems where >> _each_ processor needs _most_ of the messages. >> >> >> >
- Fwd: Replication using totem protocol Dain Sundstrom
- Re: Fwd: Replication using totem protocol Jeff Genender
- Re: Fwd: Replication using totem protocol lichtner
- Re: Replication using totem protocol Dain Sundstrom
- Re: Fwd: Replication using totem protocol Jeff Genender
- Re: Fwd: Replication using totem protocol Alan D. Cabrera
- Re: Replication using totem protocol Dain Sundstrom
- Re: Replication using totem prot... lichtner
- Re: Replication using totem ... Jeff Genender
- Re: Replication using totem ... lichtner
- Re: Replication using totem ... Jeff Genender
- Re: Replication using totem ... lichtner
- Re: Replication using totem ... Matt Hogstrom
- Re: Replication using totem ... lichtner
- Re: Replication using totem ... Jeff Genender
- Re: Replication using totem ... Jules Gosnell
- Re: Replication using totem ... Jules Gosnell
- Re: Replication using totem ... James Strachan
- Re: Replication using totem ... lichtner
- Re: Replication using totem ... James Strachan
