accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4181) Log spam regarding swappiness
Date Fri, 08 Apr 2016 21:10:26 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232930#comment-15232930
] 

Josh Elser commented on ACCUMULO-4181:
--------------------------------------

{quote}
Aaand I figured it out. I didn't have a different logging config for my monitor, which caused
it to infinitely forward the logs to itself.

Closing as this was misconfiguration error.
{quote}

Well that's a fun scenario :). Any chance you can expand on this? It sounds like something
we could prevent in the LogForwarding component.

> Log spam regarding swappiness
> -----------------------------
>
>                 Key: ACCUMULO-4181
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4181
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: monitor
>    Affects Versions: 1.7.1
>            Reporter: Michiel Vanderlee
>            Priority: Minor
>
> I notice that the monitor completely fills the log files with the following message:
>  "2016-04-07 05:21:12,955 [server.Accumulo] WARN : System swappiness setting is greater
than ten (30) which can cause time-sensitive operations to be delayed.  Accumulo is time sensitive
because it needs to maintain distributed lock agreement.."
> If I see this once during startup is enough, I don't need it to fill 10 log files of
a 1GB each within 3 days



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message