[
https://issues.apache.org/jira/browse/STORM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626643#comment-14626643
]
ASF GitHub Bot commented on STORM-937:
--------------------------------------
GitHub user rfarivar opened a pull request:
https://github.com/apache/storm/pull/631
[STORM-937] Changing the log level from info to debug
This is to reduce the noisiness of supervisor logs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rfarivar/storm STORM-937
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/631.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #631
----
commit 2d030413ab651140a3dd3655673b7bb81c1ce202
Author: rfarivar <rfari...@yahoo-inc.com>
Date: 2015-07-14T16:51:59Z
Changing the log level from info to debug
----
> StormBoundedExponentialBackoffRetry too noisy, lower log level
> --------------------------------------------------------------
>
> Key: STORM-937
> URL: https://issues.apache.org/jira/browse/STORM-937
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Reza Farivar
> Assignee: Reza Farivar
> Priority: Minor
>
> The supervisor logs are currently overpopulated with log messages similar to
> this:
> 2015-07-10 18:12:06.723 b.s.u.StormBoundedExponentialBackoffRetry [INFO] The
> baseSleepTimeMs [2000] the maxSleepTimeMs [60000] the maxRetries [5]
> The log level in the StormBoundedExponentialBackoffRetry is currently at info
> level. It seems it can be safely lowered to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
