| Summary: | pmlogger sends PROFILE PDU unnecessarily every fetch | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Frank Ch. Eigler <fche> |
| Component: | pcp | Assignee: | pcp-maint <pcp-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 29 | CC: | fche, kenj, lberk, mgoodwin, nathans, pcp |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-03-05 03:28:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Frank Ch. Eigler
2016-09-28 15:04:37 UTC
Frank,
Not sure there is a lot we can do about this.
Consider this pmlogger config
log mandatory on 5min {
kernel.all.load ["5 minute"]
}
log mandatory on 1min {
kernel.all.load ["1 minute"]
}
Given that there is one context for pmlogger it does not have much choice other than to send the relevant profile before each fetch.
Ken, even in that case, pmlogger could - use two contexts (one per time period or per profile setting or similar) or - track profile status quo on the client side, and thus note in your example that four of the five "1 minute" fetches don't need profile resets between them We wouldn't have to find the optimal settings to improve significantly upon the pessimal ones currently in effect. This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. This is a non-issue in practice, and is unlikely to ever get on the radar of pcp engineers. Closing. |