Thanks for the replies!
Other than waiting for the fix Adam talked about to make it to our
environment, what else could we possibly do to alleviate the problem?
We were thinking of having a monitor on the number of couchjs
processes and/or their memory usage and bounce couch when needed. We'd
rath
Hah, thanks Adam,
this is exactly the email I hoped to see by CCing dev@ :)
Cheers
Jan
--
On 16 Apr 2011, at 15:09, Adam Kocoloski wrote:
> I've seen this bug in the wild. I haven't been able to track down the exact
> root cause, but the various ets tables in couch_query_servers get out of s
I've seen this bug in the wild. I haven't been able to track down the exact
root cause, but the various ets tables in couch_query_servers get out of sync
with one another - one table will think there are no available processes and
will cause new ones to be spawned but the others will still have
Hi Ning,
the correlation between couchjs and HTTP requests is that whenever a
request needs couchjs for anything, it will use one that is around and
idle. When CouchDB starts, none are idle and it will for and exec a
new couchjs process. A couchjs process is not idle when a request is
using it. S
