You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2012/10/30 17:10:12 UTC
[jira] [Created] (QPID-4403) C++ Broker Timer warnings are still
too verbose and frequent
Chuck Rolke created QPID-4403:
---------------------------------
Summary: C++ Broker Timer warnings are still too verbose and frequent
Key: QPID-4403
URL: https://issues.apache.org/jira/browse/QPID-4403
Project: Qpid
Issue Type: Improvement
Components: C++ Broker
Affects Versions: 0.18
Reporter: Chuck Rolke
Continuing issue QPID-3476.
1) Further reducing the timer warning message log level.
Between 0.12 and 0.13 timer warning messages were demoted from warning to informational log levels. In 0.19 the external store produces overrun info messages every time leading to log file bloat.
The proposal here is to demote the information statements to debug statements for the same reasons that they were demoted from warnings:
"Demoting the warnings to debug statements would avoid undue alarm and prevent excess noise in log files. Should there be a need to see the information it is a lot easier to enable it (--log-enable debug+:Timer) than it is to turn it off at present."
2) Increasing the timer warning interval.
Another consideration is to change the hard-coded five second warning interval to something longer. I suggest that one minute would be a good choice. The timer warning code already accumulates the number of warnings for the warning interval to prevent a flood of warnings. Increasing the warning interval further reduces the flood.
3) Performance improvement.
When Issue 3476 was patched from warning to info there was a corresponding QPID_LOG_TEST in Timer.cpp that was not patched. This causes the late and overrun calculations to run even though the results will never be logged.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Assigned] (QPID-4403) C++ Broker Timer warnings are still
too verbose and frequent
Posted by "Justin Ross (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross reassigned QPID-4403:
---------------------------------
Assignee: Chuck Rolke
> C++ Broker Timer warnings are still too verbose and frequent
> ------------------------------------------------------------
>
> Key: QPID-4403
> URL: https://issues.apache.org/jira/browse/QPID-4403
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: 0.18
> Reporter: Chuck Rolke
> Assignee: Chuck Rolke
>
> Continuing issue QPID-3476.
> 1) Further reducing the timer warning message log level.
> Between 0.12 and 0.13 timer warning messages were demoted from warning to informational log levels. In 0.19 the external store produces overrun info messages every time leading to log file bloat.
> The proposal here is to demote the information statements to debug statements for the same reasons that they were demoted from warnings:
> "Demoting the warnings to debug statements would avoid undue alarm and prevent excess noise in log files. Should there be a need to see the information it is a lot easier to enable it (--log-enable debug+:Timer) than it is to turn it off at present."
> 2) Increasing the timer warning interval.
> Another consideration is to change the hard-coded five second warning interval to something longer. I suggest that one minute would be a good choice. The timer warning code already accumulates the number of warnings for the warning interval to prevent a flood of warnings. Increasing the warning interval further reduces the flood.
> 3) Performance improvement.
> When Issue 3476 was patched from warning to info there was a corresponding QPID_LOG_TEST in Timer.cpp that was not patched. This causes the late and overrun calculations to run even though the results will never be logged.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org