[
https://issues.apache.org/jira/browse/COUCHDB-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484483#comment-13484483
]
Robert Newson commented on COUCHDB-1569:
----------------------------------------
I've been pondering this on and off today. There are other conditions in the
compaction daemon that might warrant ERROR level, like when it cancels a
compaction because the time period it's allowed to run is has expired. Manually
started compactions that would consume all remaining disk space will *not* log
at ERROR if you start them either.
So, on reflection, I think this is really an INFO level thing after all (if
only because we can't make it ERROR level with any consistency).
What's truly missing is the ability to change log levels by module. i.e, I'd
like to see INFO level from couch_compaction_daemon but not from couch_httpd.
> Low diskspace warning for compaction should be logged at error level
> --------------------------------------------------------------------
>
> Key: COUCHDB-1569
> URL: https://issues.apache.org/jira/browse/COUCHDB-1569
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Affects Versions: 1.2
> Reporter: Nils Breunese
> Priority: Trivial
> Fix For: 1.3
>
> Attachments: patch.txt, patch_updated.txt
>
>
> In production we're running CouchDB at log level 'error', because running at
> 'info' is too verbose for production. We suspect automatic compaction might
> not be running due to low diskspace.
> http://wiki.apache.org/couchdb/Compaction#Automatic_Compaction says: "When
> there's not enough free disk space to compact a particular database or view
> index, a warning message is logged." But there is no warning log level in
> CouchDB as far as I know and the can_db_compact function in
> src/couchdb/couch_compaction_daemon.erl seems to log the message about
> diskspace being too low at info level. Could this be changed to error level?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
