Red Hat Bugzilla – Bug 1282764
[RFE][scale] Visualize the number of queued SPM calls on RHEV-M in the logs
Last modified: 2016-08-23 16:30:42 EDT
Description of problem:
When using RHEV for a test lab, where each test involves the creation of, and then the removal of a VM, the API allows for loading the environment heavily, including storage. For this use case, the goal is to load the environment, but to keep it running stable.
When storage is loaded and responds slower than usual, the requests may be queued on the manager. The logs do not contain information, to get an idea about this, easily.
This RFE is about adding information in the engine log file, when requests to the SPM are queued until other requests return.
Version-Release number of selected component (if applicable):
Running storage tasks in parallel
Steps to Reproduce:
This request is related to the following issues:
bz#1275736 - Transaction scope is too large for SPM commands
bz#1277057 - Unfair queuing mechanism on the manager for handling SPM requests
A log was added in DEBUG logging mode.
Bug[RFE] verified on RHEVM - 4.0.2-0.2.rc1.el7ev
Changed engine log level to DEBUG
Ran REST API script which removes templates using 5 concurrent threads.
We can see expected messages in engine.log file such as:
2016-07-19 09:05:05,396 DEBUG [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData] (org.ovirt.thread.pool-6-thread-9) [29f4512] Waiting on other task to finish (0 additional threads are queued)
2016-07-19 09:05:05,397 DEBUG [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData] (org.ovirt.thread.pool-6-thread-15) [6fa566a6] Waiting on other task to finish (1 additional threads are queued)
Attached engine.log file
Test started at 2016-07-19 09:04:54
I think,we can closed bug.
Created attachment 1181643 [details]
Engine.log DEBUG log level
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.