accumulo-notifications mailing list archives

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

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

Michiel Vanderlee commented on ACCUMULO-4181:
---------------------------------------------

I looked at the code, and while I could create the suggested property, I don't think this
is the issue here.

My other servers run fine and only log the message every 10 minutes (144 times per day).
Executing: "grep -o 'System swappiness setting is greater than ten' /opt/accumulo/logs/monitor_mantl-michiel2-storage-003.l*
| wc -l" returned 44479916, or 44 million logs.
The VM was only created < 24 hours before that, so I highly doubt that it's the 'monitorSwappiness'
method itself.

Since it's only the monitor I wonder if it has anything to do with the log forwarding.
Looking in a log file you can see that the timestamps are all mangled, as if the monitor is
constantly rewriting the same info:
...
2016-04-05 08:13:13,558 [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.
2016-04-04 22:15:59,110 [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.
2016-04-05 03:23:13,452 [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.
2016-04-05 03:25:59,304 [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
...

In fact, when I do a search for a timestamp I see many occurences of that timestamp. I.e.:
"2016-04-05 08:13:13,558" has 247518 occurrences across all monitor log files.

> 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