hadoop-zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Reed <br...@yahoo-inc.com>
Subject Re: Share Zookeeper instance and Connection Limits
Date Wed, 16 Dec 2009 22:06:50 GMT
I agree with Ted, it doesn't seem like a good idea to do in practice. 
however, you do have a couple of options if you are just testing things:

1) use tmpfs
2) you can set forceSync to "no" in the configuration file to disable 
syncing to disk before acknowledging responses
3) if you really want to make the disk write go away, you can modify the 
SyncRequestProcessor in the code


Ted Dunning wrote:
> I think that htis would be a very bad idea because of restart issues.  As it
> stands, ZK reads from disk snapshots on startup to avoid moving as much data
> from other members of the cluster.
> You might consider putting the snapshots and log on a tmpfs file system if
> you really, really want this.
> On Wed, Dec 16, 2009 at 1:08 PM, Thiago Borges <thborges@gmail.com> wrote:
>> Can Zookeeper ensemble runs only in memory rather than write in both memory
>> and disk? This makes senses since I have a high reliable system? (Of course
>> at some time we need a "dump" to shutdown and restart the entire system).
>> Well, the disk IO or network first limits the throughput?
>> Thanks for you quick response. I'm studding Zookeeper in my master thesis,
>> for coordinate distributed index structures.

View raw message