[GitHub] wohali edited a comment on issue #1579: Autocompaction never triggered in Couch v2.2

[GitBox <gi...@apache.org>]

wohali edited a comment on issue #1579: Autocompaction never triggered in Couch v2.2
URL: https://github.com/apache/couchdb/issues/1579#issuecomment-442659906
 
 
   @regner Indeed, 2.2 introduced a bunch of new options that had the overall effect of slowing down database/view compactions as @nickva says above. You might want to have a read through: http://docs.couchdb.org/en/stable/whatsnew/2.2.html and specifically:
   
   > The compaction daemon now has a snooze period, during which it waits to start the next compaction after finishing the previous one. This value is useful in setups with many databases (e.g. with couch_peruser) or many design docs, which can cause a CPU spike every check_interval seconds. The setting can be adjusted in your local ini file via [compaction_daemon] snooze_period. The current default is a 3 second pause.
   > The check_interval has been raised from 300 seconds to 3600 seconds.
   >  A notice-level log about closing view indexes has been demoted to the debug level. In a sceario with many design docs, this would createsignficant load on the logging subsystem every [compaction_daemon] check_interval for no discernible benefit.
   
   These changes were made because busy clusters couldn't handle the default compaction daemon load. Perhaps your cluster can?
   
   I agree there is probably an enhancement request here re: picking up where we left off after last runtime, so we don't always start with the same database. I'll file a separate request.
   
   Does the above information resolve your problem?

----------------------------------------------------------------
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