[GitHub] mtabb13 opened a new issue #869: beam.smp spikes and eats all available CPU

[gi...@git.apache.org]

mtabb13 opened a new issue #869: beam.smp spikes and eats all available CPU
URL: https://github.com/apache/couchdb/issues/869
 
 
   This is a production system, and a bit frustrated, sorry if this in the wrong spot.  Don't know where else to look.  I have searched high and low for answers, posted in the IRC, and nothing.  In a nutshell, I have a 2 node cluster running, with cpu at normal levels, I do some inserts and queries, seriously, not a heavy load at all.  The database(s) being used have ~39 million rows and some views, but mostly mango indexes.  After ~12-20 insert/queries, the beam.smp process takes off.  The current request to insert that caused the spike, never returns and times out.  I have no idea where else I can look for clues.  The logs are debug level and verbose, and everything looks pretty normal.  The 2 nodes are very large 1TiB machines with 4cpu/4cores each.  Resources are not an issue at all.  Something is fundamentally wrong here, but don't know where to look.  I have tweaked and turned every possible knob there is in the couch config, and have had no results
   
   Version used: 2.0
   Operating System and version (desktop or mobile): Ubuntu 16
 
----------------------------------------------------------------
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