Comment 10 for bug 1719236

Revision history for this message
Arvind (arvindv) wrote :

Hi Vijaya Kumar,

sorry for the delayed response.
Trying to understand the setup and queries issued more...

1) Are we having control and config on the same node or are they on different nodes?
2) Can you explain a bit about the script they are using to query analytics ?
We want to understand how are the queries being issued. Are the issuing individual GET request
for the VN and VMI and then timing the entire operation. Do they wait for individual requests to succeed and then issue the newer one ? Are they trying to determine the time taken to issue (300,600) GET requests vs (1500,3000) GET requests vs (3000, 6000) GET requests. [If there are more API requests more time will be taken, so can u clarify if my understanding of the issue is wrong]

3) Do they give time after each of the control-node shutdown and issuing query against analytics
This can be checked by looking at the redis.log in analytics node and make sure no deletes are happening before issuing the query against analytics.

4) Also the messages u have reported are unrelated to the issue reported by the customer. You are experiencing connectivity issues in analytics to redis. Before trying to issue queries, make sure contrail-status on analytics is ok.
Thanks
Arvind