Unsolved
This post is more than 5 years old
7 Posts
0
1588
Having problems with --query_network_latency_meters
I just deployed a new scaleio fabric on vmware, using 2.0.13000_211, over vmware esxi
Having trouble with the scli command --query_network_latency_meters
The output shows the latency to itself (see below), is the display just showing the wrong addresses, and is the data accurate.
I was expecting to run this command on SDS .18, and see the output for SDS .18 to both SDS .20 and .21.
Anymore insight into the output, is that a 30 second average latency? How it is calculated
ScaleIO-172-24-99-9:~ # scli --query_network_latency_meters --sds_ip 1.1.1.18
SDS with IP 1.1.1.18 (port 7072) returned information on 2 SDSs
SDS 1.1.1.18
Average IO size: 13.0 KB (13312 Bytes)
Average latency (micro seconds): 1304
SDS 1.1.1.18
Average IO size: 3.0 KB (3072 Bytes)
Average latency (micro seconds): 1071
ScaleIO-172-24-99-9:~ # scli --query_network_latency_meters --sds_ip 1.1.1.20
SDS with IP 1.1.1.20 (port 7072) returned information on 2 SDSs
SDS 1.1.1.20
Average IO size: 7.0 KB (7168 Bytes)
Average latency (micro seconds): 757
SDS 1.1.1.20
Average IO size: 4.0 KB (4096 Bytes)
Average latency (micro seconds): 2218
ScaleIO-172-24-99-9:~ # scli --query_network_latency_meters --sds_ip 1.1.1.21
SDS with IP 1.1.1.21 (port 7072) returned information on 2 SDSs
SDS 1.1.1.21
Average IO size: 1.0 KB (1024 Bytes)
Average latency (micro seconds): 932
SDS 1.1.1.21
Average IO size: 4.0 KB (4096 Bytes)
Average latency (micro seconds): 1631
Thanks Simon
Ken.Whitehead
24 Posts
0
August 20th, 2017 11:00
I am not be understanding the question here but the outputs show less than 3 milliseconds of latency for each of these SDS.
Are you seeing something that is reporting 30 Seconds of latency?
simon13
7 Posts
0
August 20th, 2017 12:00
Thanks Ken,
Sorry I'll be more clear, when I ran the command for say .21, the output showed SDS .21, and SDS .21 (it did not show .20 and .18 in the output). I wanted to see the latency from .21 to .18 and .21 to .20.
I made calls via the API but got errors and started to wonder if this is actually working. I'll post the API response too later.
See below, ran the command on .21 and it does not mention to which SDS the latency is measured with
Finally any idea what period the latency is measure over?
ScaleIO-172-24-99-9:~ # scli --query_network_latency_meters --sds_ip 1.1.1.21
SDS with IP 1.1.1.21 (port 7072) returned information on 2 SDSs
SDS 1.1.1.21
Average IO size: 1.0 KB (1024 Bytes)
Average latency (micro seconds): 932
SDS 1.1.1.21
Average IO size: 4.0 KB (4096 Bytes)
Average latency (micro seconds): 1631
simon13
7 Posts
0
August 20th, 2017 16:00
Here is the REST api info
For example this works (using Postman just to test it out)
https://172.24.99.7:443/api/instances/Sds::b3b57d7d00000002/relationships/Statistics
{
"pendingMovingOutBckRebuildJobs": 0,
"secondaryVacInKb": 70041600,
"numOfDevices": 2,
........etc
But this does not work
https://172.24.99.7:443/api/instances/Sds::b3b57d7d00000002/action/querySdsNetworkLatencyMeters
{
"message": "Method Not Allowed",
"httpStatusCode": 405,
"errorCode": 0
}
Avinash V
91 Posts
0
August 31st, 2017 07:00
Seems to be a Bug. Please open a call with ScaleIO Support