You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/04/29 18:52:38 UTC

[GitHub] wohali commented on issue #1298: Views fail to index with timeout prior to os_process_timeout elapsing

wohali commented on issue #1298: Views fail to index with timeout prior to os_process_timeout elapsing
URL: https://github.com/apache/couchdb/issues/1298#issuecomment-385272782
 
 
   @javamonn 
   
   You're right in that the cpu_sup process failing suggests that your instance is heavily CPU constrained. The 5 second timeout may mean that couchjs is failing to even start up correctly - you're not even getting an initial "hello" handshake back from that spawned process.
   
   Are you able to increase the CPU allocation for your instance? If so, please do. CouchDB runs best with 4 or more cores allocated.
   
   We are tracking numerous situations in which CouchDB deployed in containers is simply unreliable. We don't have enough people to debug these scenarios right now. So far, in most cases it's simply too few CPU or RAM resources being allocated.
   
   If you need a guaranteed stable CouchDB we recommend deploying it in the traditional fashion on dedicated VMs or bare metal if possible.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services