Yes, I am working on a similar setup. I ran into replication problems as the number of databases increased. I've switched to the 1.2 trunk build as replication has been radically modified and seems more reliable.
On 5 January 2012 12:53, Gregor Martynus <[email protected]> wrote: > Thanks all for your responses! The app is hosted at iris couch, I'm sure > that Jason will respond to the technical suggestions, thanks so much! > > I've a monitoring in place that checks the _log once per minute and > notifies me if there is any error. I also checked it manually. There is no > error. I'm not sure if there are other system logs we could log into, but > the logs that are exposed via '/_log' did not show any errors. > > I'm still wondering if there is anybody else with a similar way to use > couchDB as I am, with many databases (e.g. per user) and tons of (internal) > continuous replications. Is this not a setup that couchDB supports / > encourages? > > On Thu, Jan 5, 2012 at 10:18 AM, Gregor Martynus <[email protected] > >wrote: > > > I experience massive reliability issues with continuous replications in > my > > app. Each user has an own profile db with a continuous replication to a > > central database. Numbers: ~1800 dbs & ~2600 continuous replications > > (using _replicator db), ~200 did not get started. > > > > My hope is that others faced these issues before and found ways to fix or > > work around them. So if you are a developer or know developers that have > a > > similar couchDB setup, would you mind to get me in touch? Thanks for your > > help! > > > > Tech info: > > couchDB 1.1.1 (iriscouch) > > max_dbs_open is set to 5000 > > no errors show up in _log > > _replicate does not accept POST requests anymore > > new replications from _replicator docs do not get picked up > > >
