On Mon, May 24, 2010 at 9:25 AM, Matteo Redaelli <matteo.redae...@gmail.com> wrote: > Hello > > I currectly use couchdb as repository for my the Ebot project ( > http://www.redaelli.org/matteo-blog/projects/ebot/). My db is getting more > and more bigger.. > > rw-r-r— 1 couchdb 81099821870 2010-05-23 ebot.couch > rw-r-r— 1 couchdb 392589468 2010-05-23 .ebot_design > > For better scalability it would be better that > > 1) couchdb wrote data not only to one single file but to different files to > DIFFERENT directories: in this way it would be easier to add new devices, > file systems ... > 2) couchdb distributed (non only replicated) data among several instances. > like Riak and other NOSQL databases > > Do you think that these 2 features could be implemented in the next near > future? or are they out of the scope of couchdb project? > > Thanks in advance
Hi Matteo, you should try CouchDB-Lounge for your setup. It's not yet as smooth as riak or cassandra do partitioning (and auto-balancing, etc.) but it should get you started as well. Further reading: http://tilgovi.github.com/couchdb-lounge/ http://groups.google.com/group/couchdb-lounge http://till.klampaeckel.de/blog/archives/84-A-toolchain-for-CouchDB-Lounge.html CouchDB-Lounge is nginx, a twistd daemon and several CouchDB servers which can all run on the same server, of course. It'll help you utilize all the resources until you outgrow your current server and then it's trivial to move a couple of your shards to another one and spread it out. CouchDB-Lounge currently doesn't do auto-balancing which is useful if you want to add another server to your cluster. Instead the proposal is to overshard (run more CouchDB instances than you need on the same server) or add another lounge to the cluster and partition "behind" it. If you're running into space issues right now it helps to move the views (.ebot_*) to another disk and configure view_index_dir in your local.ini. Hope that helps! Cheers, Till
