You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2013/07/16 09:22:48 UTC
[jira] [Commented] (CLOUDSTACK-3108) Disk related statistics of a
VM always show 0 values
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709565#comment-13709565 ]
Wei Zhou commented on CLOUDSTACK-3108:
--------------------------------------
Animesh,
I picked it up.
The data collection mechanisms in hypervisors are different. KVM provides traffic data aggregation value , and Vmware/Xen provide traffic rate value.
Hence, we can collect aggregation value for KVM only, and disk I/O statistics (CLOUDSTACK-1192) supports KVM only.
Stats Collector is ok for KVM (it collects aggregation value). I will change the codes to show polling traffic rate value for Vmware/Xen.
-Wei
> Disk related statistics of a VM always show 0 values
> -----------------------------------------------------
>
> Key: CLOUDSTACK-3108
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3108
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Storage Controller
> Affects Versions: 4.2.0
> Environment: build:
> CloudPlatform-4.2-117-rhel6.3.tar.gz
> Reporter: shweta agarwal
> Assignee: Wei Zhou
> Priority: Critical
> Fix For: 4.2.0
>
>
> Repro steps:
> 1. Set global configuration value for storage.stas to 600 milliseconds or other small value and restart Management server
> 2. Create a VM
> 4. Create Some data on a VM (create a data heavy file)
> 5. Wait for storage collector thread to run
> Bug:
> Even after storage stats collector thread runs Disk Read, Disk write shows values a zero.
> Expectations:
> Disk read , disk write stats for VM should show correct value.
> I waited for several Stats collector thread to collect data but still value in VM shows Zero
> For example:
> VM stats shows
> API : http://10.147.38.141:8080/client/api?command=listVirtualMachines&details=stats&id=c448201a-9fc5-4cc1-ab28-c8cd2a53594d&response=json&sessionkey=4xWeT9Rw4XpRnWMGa1yIqr2vYSA%3D&_=1371794494563
> Response:
> { "listvirtualmachinesresponse" : { "count":1 ,"virtualmachine" : [ {"id":"c448201a-9fc5-4cc1-ab28-c8cd2a53594d","name":"c448201a-9fc5-4cc1-ab28-c8cd2a53594d","account":"admin","domainid":"9df32920-d98f-11e2-95e7-0682fe000017","domain":"ROOT","created":"2013-06-20T18:16:16+0530","state":"Running","haenable":false,"zoneid":"0d3e68a9-4f66-4077-a934-6a07b7bde4d1","zonename":"xen","hostid":"897004e4-4eab-471a-88c6-0f9ad84386c0","hostname":"Rack1Pod1Host27","cpuused":"0%","networkkbsread":39873,"networkkbswrite":1336,"diskkbsread":0,"diskkbswrite":0,"diskioread":0,"diskiowrite":0,"guestosid":"9ea5e3d0-d98f-11e2-95e7-0682fe000017","securitygroup":[],"nic":[{"id":"832205d4-b9ed-4e35-93fe-25dfa51afe43","networkid":"4bda1bc0-8c1b-4368-8ee9-e7d32f842ca9","networkname":"vv","netmask":"255.255.255.0","gateway":"10.0.4.1","ipaddress":"10.0.4.237","isolationuri":"vlan://1041","broadcasturi":"vlan://1041","traffictype":"Guest","type":"Isolated","isdefault":false,"macaddress":"02:00:7a:18:00:03"},{"id":"6613398e-b652-41e7-8ca3-77f0d913acc0","networkid":"867ab04e-fae0-4e0d-aea0-c3e135273b1a","networkname":"tier1","netmask":"255.255.255.0","gateway":"10.0.3.1","ipaddress":"10.0.3.121","isolationuri":"vlan://1046","broadcasturi":"vlan://1046","traffictype":"Guest","type":"Isolated","isdefault":false,"macaddress":"02:00:40:00:00:01"}],"hypervisor":"XenServer","instancename":"i-2-8-VM","tags":[],"affinitygroup":[],"displayvm":true} ] } }
> Where as VM shows following file sizes
> ls -ltr
> -rw-r--r-- 1 root root 3965 Jun 20 18:30 ter
> -rw-r--r-- 1 root root 3965 Jun 20 18:30 ter1
> -rw-r--r-- 1 root root 206180 Jun 20 18:31 ter4
> -rw-r--r-- 1 root root 206180 Jun 20 18:31 ter5
> -rw-r--r-- 1 root root 9071920 Jun 20 18:31 ter3
--
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