On Tue, Mar 3, 2009 at 9:33 PM, Ted Dunning <ted.dunn...@gmail.com> wrote:
> zookeeper is not really what you would call a scalable system because all
> transactions that are updates go through the leader for serialization.
> Zookeeper is, instead, a high throughput HA system. That said, the
> throughput of a modest zookeeper cluster is fairly prodigous so for the
> normal application of coordinating a large cluster, these limits are beyond
> what just about anyone needs.
> For other uses, though, 50 K updates per second wouldn't cut it.
I understand that Google uses Chubby (a ZooKeeper clone... or vice versa :-)
) as the coordination mechanism for Big Table. Do you have any insight into
Chubby's performance characteristics... and if it would be possible to build
a Big Table clone that had scalability characteristics of Big Table with
ZooKeeper as the underlying coordinator?
> Sent from my iPhone
> On Mar 3, 2009, at 17:30, Chad Harrington <charring...@datascaler.com>
> Clearly Zookeeper can handle ensembles of a dozen or so servers. How
>> an ensemble can one build with Zookeeper? 100 servers? 10,000 servers?
>> Are there limitations that make the system unusable at large numbers of
>> Chad Harrington
>> DataScaler, Inc.
>> 201A Ravendale Dr.
>> Mountain View, CA 94043
>> Phone: 650-515-3437
>> Fax: 650-887-1544
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp