I should add that if you cannot afford to upgrade to 0.11 for whatever reason I have a backport I can provide for 0.10.1.
On Tue, Mar 23, 2010 at 13:58, Randall Leeds <[email protected]> wrote: > Hi Germain, > > Your use case sounds very reasonable and there are similar production > setups in use today. I have seen similar problems in production here > and authored a patch that has made it into 0.11 that should help. > http://issues.apache.org/jira/browse/COUCHDB-597 > > However, at least one bug report remains claiming that this does not > fix everything: > https://issues.apache.org/jira/browse/COUCHDB-691 > > I'll try to look into it further after this week if no one else gets > there first. But if you can afford to, please test the 0.11 release > artifacts (should be stable, currently under vote for release on the > development list) and re-open COUCHDB-597 or just report your findings > here. > > Find the 0.11 release artifacts here: > http://mail-archives.apache.org/mod_mbox/couchdb-dev/201003.mbox/%[email protected]%3e > > Alternatively, wait a day or two and the vote should (hopefully) pass, > making it an official release. > > -Randall > > On Tue, Mar 23, 2010 at 09:41, Germain Maurice > <[email protected]> wrote: >> Hi Jan, >> >> Yes i forgot to say we are using CouchDB 0.10.1 on Debian 5.0 lenny. >> >> >> >> Jan Lehnardt a écrit : >>> >>> HI Germain, >>> >>> which CouchDB version are you running? >>> >>> Cheers >>> Jan >>> -- >>> >>> On 23 Mar 2010, at 02:14, Germain Maurice wrote: >>> >>> >>>> >>>> Hi everybody, >>>> >>>> We have a database with more than 8 millions of documents and the size is >>>> more than 450 GB. I wonder if it's a good choice to have all of our docs in >>>> only one file of this size. >>>> >>>> We have issues with replication through every time. We tried both one >>>> shot and continuous replication and we got req_timedout followed by a >>>> couchdb crash. We opened reports bugs you can see here : >>>> https://issues.apache.org/jira/browse/COUCHDB-690 and >>>> https://issues.apache.org/jira/browse/COUCHDB-701 >>>> >>>> Another issue is compaction which doesn't work fine on one of my host. >>>> The compaction is launched on a database which has more than 100 000 >>>> documents (10GB) The compaction starts up, works, and after a while, >>>> stops without any warning or alerts. On a other host the same database >>>> was well compacted. >>>> >>>> We really wonder how couchdb is used in a production environment. How >>>> many documents do you store ? Do you use big databases or small >>>> databases (file size i mean) ? Embedded replication or not ? Compaction >>>> is efficient or not ? >>>> >>>> We are trying to make some developpement in order to avoid the issues we >>>> encounted, we would like some feedback about the best practices in >>>> environment production. >>>> >>>> Best regards, >>>> Germain >>>> >>> >>> >> >> >> -- >> Germain Maurice >> Administrateur Système/Réseau >> Tel : +33.(0)1.42.43.54.33 >> >> http://www.linkfluence.net >> **linkfluence news & events** >> 2009 excellence award nominee from ESOMAR >> 2009 marketing research silver award from semo & marketing magazine (France) >> 2009 european excellence award recipient (PR evaluation, wahlradar.de, joint >> project with Publicis Consultants) >> >> >
