[
https://issues.apache.org/jira/browse/CASSANDRA-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378733#comment-14378733
]
Benedict commented on CASSANDRA-8584:
-------------------------------------
bq. who really reads log files
It seems like this conversation is heading very much towards that general
analysis of logging, which is probably best to happen on its own ticket. At the
very least on CASSANDRA-9029, which will be more clearly related to any general
topic.
I agree that logging is not the best way to manage bad cluster states, since
most people don't monitor their logs. Unfortunately we have no better (or any
other) way of alerting users to significant problems. This is perhaps a third
line of enquiry to open: is there a better way for us to report significant
events that cluster owners should respond to? I'm not aware of a good
standardised API for this.
bq. amount of messages is is the level of importance
If we choose to expand the NoSpamLogger's functionality, I also agree it makes
sense for it to support aggregation of log messages over some time horizon, so
if any log messages are suppressed, a tally count of those suppressed is
periodically emitted. But I don't consider this super pressing. Seeing these
messages every minute in the log is notification enough that the problem is
prevalent.
> Add strerror output on failed trySkipCache calls
> ------------------------------------------------
>
> Key: CASSANDRA-8584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8584
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Joshua McKenzie
> Assignee: Joshua McKenzie
> Priority: Trivial
> Fix For: 2.1.4
>
> Attachments: 8584_v1.txt, NoSpamLogger.java, nospamlogger.txt
>
>
> Since trySkipCache returns an errno rather than -1 and setting errno like our
> other CLibrary calls, it's thread-safe and we could print out more helpful
> information if we failed to prompt the kernel to skip the page cache. That
> system call should always succeed unless we have an invalid fd as it's free
> to ignore us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
