New commit detected on ManageIQ/manageiq/fine: https://github.com/ManageIQ/manageiq/commit/6332db37fc931b7c4acc135d0a56dfe96f55d883 commit 6332db37fc931b7c4acc135d0a56dfe96f55d883 Author: Gregg Tanzillo <gtanzill> AuthorDate: Wed Jun 14 11:12:57 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Fri Jun 16 16:09:36 2017 -0400 Merge pull request #15312 from jntullo/bz/purge_timeout Increase timeout for metric purging (cherry picked from commit 62719214d86bf68b169571af9a761fea6331f5f4) https://bugzilla.redhat.com/show_bug.cgi?id=1462358 app/models/metric/purging.rb | 5 +++++ app/models/vmdb_metric/purging.rb | 7 ++++++- config/settings.yml | 4 +++- spec/models/metric/purging_spec.rb | 33 +++++++++++++++++++-------------- 4 files changed, 33 insertions(+), 16 deletions(-)
Verified on 5.8.1.0. Metric purging now uses 20 minute timeout, e.g., **** [----] I, [2017-07-03T12:50:04.889211 #3062:459138] INFO -- : MIQ(MiqQueue.put) Message id: [175205], id: [], Zone: [default], Role: [], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [VmdbDatabaseMetric.purge_hourly], Timeout: [1200], Priority: [100], State: [ready], Deliver On: [], Data: [], Args: [2017-01-04 16:50:04 UTC] [----] I, [2017-07-03T13:43:31.468162 #3062:459138] INFO -- : MIQ(MiqQueue.put) Message id: [177438], id: [], Zone: [default], Role: [], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [Metric::Purging.purge_realtime], Timeout: [1200], Priority: [100], State: [ready], Deliver On: [], Data: [], Args: [2017-07-02 17:43:31 UTC] **** After changing the database.metrics_history.queue_timeout and performance.history.queue_timeout settings to 10.minutes and restarting EVM server processes, the timeouts change to 10 minutes.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1758