Created attachment 651823[details]
logs
Description of problem:
I blocked connectivity from the spm to the iso domain only and once the domain becomes inactive in engine the performance for SPM tasks has dropped.
Version-Release number of selected component (if applicable):
vdsm-4.9.6-44.0.el6_3.x86_64
How reproducible:
100%
Steps to Reproduce:
1. block connectivity to the iso domain from the hosts.
2. after domain becomes inactive start sending commands to the spm.
3.
* I don't think that its related to the performance changes but after the domain was inactive I also added my setup to the qa domain (using rhevm-manage-domains tool).
Actual results:
spm commands take much longer because iso domain is reported as stuck in vdsm log
Expected results:
we should not have any performance issues because a domain is inactive.
Additional info: logs
in attached logs:
we can see that CreateImageVDSCommand is sent to vdsm at 10:56:24 but the CreateImageVDSCommand is only issued at 10:58:04
Comment 3Federico Simoncelli
2012-12-21 16:28:55 UTC
commit 3ded8c7e1671c6a60ec6fe43ae250329cd6bb4ae
Author: Federico Simoncelli <fsimonce>
Date: Fri Dec 21 11:18:29 2012 -0500
stats: compute the iso prefix asynchronously
The iso prefix must be computed asynchronously because in any other
synchronous operation (e.g.: connectStoragePool, getInfo) vdsm cannot
risk to stop and wait for the iso domain to report its prefix (since
it might be unreachable).
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=880098
Change-Id: I09b7be78da544547a6ed9d5b440bdb0037004c16
Signed-off-by: Federico Simoncelli <fsimonce>
http://gerrit.ovirt.org/#/c/10305/
Created attachment 651823 [details] logs Description of problem: I blocked connectivity from the spm to the iso domain only and once the domain becomes inactive in engine the performance for SPM tasks has dropped. Version-Release number of selected component (if applicable): vdsm-4.9.6-44.0.el6_3.x86_64 How reproducible: 100% Steps to Reproduce: 1. block connectivity to the iso domain from the hosts. 2. after domain becomes inactive start sending commands to the spm. 3. * I don't think that its related to the performance changes but after the domain was inactive I also added my setup to the qa domain (using rhevm-manage-domains tool). Actual results: spm commands take much longer because iso domain is reported as stuck in vdsm log Expected results: we should not have any performance issues because a domain is inactive. Additional info: logs in attached logs: we can see that CreateImageVDSCommand is sent to vdsm at 10:56:24 but the CreateImageVDSCommand is only issued at 10:58:04