[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583643#comment-13583643
 ] 

Min Chen commented on CLOUDSTACK-1290:
--------------------------------------

Please provide your environment details, including MS, db, etc. Also provide 
the exact listNetwork API invocation, I will take a look. How many network do 
you have in your system?
                
> listNetoworks API takes too long to respond
> -------------------------------------------
>
>                 Key: CLOUDSTACK-1290
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1290
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: API
>    Affects Versions: 4.1.0
>         Environment: ASF 4.1
>            Reporter: Sanjeev N
>            Assignee: Min Chen
>            Priority: Critical
>             Fix For: 4.1.0
>
>         Attachments: createEgressFirewallRuleAPI.PNG, listNetworksAPI.PNG
>
>
> lintNetoworks API takes too long to respond. In face most of the list APIs 
> are taking too long and UI becomes inaccessible during this time. It took 
> more than 5 mins to get the response.
> Most of the times we see "Agent behind ping" messages on the console.
> Following are the few messages captured:
> WARN  [agent.manager.AgentManagerImpl] (AgentTaskPool-10:) Agent state cannot 
> be determined, do nothing
> INFO  [agent.manager.AgentMonitor] (Thread-8:) Found the following agents 
> behind on ping: [1]
> INFO  [agent.manager.AgentManagerImpl] (AgentTaskPool-11:) Investigating why 
> host 1 has disconnected with event PingTimeout
> INFO  [agent.manager.AgentManagerImpl] (AgentTaskPool-11:) The state 
> determined is Up
> INFO  [agent.manager.AgentManagerImpl] (AgentTaskPool-11:) Agent is 
> determined to be up and running
> INFO  [agent.manager.AgentMonitor] (Thread-8:) Found the following agents 
> behind on ping: [4]
> INFO  [agent.manager.AgentManagerImpl] (AgentTaskPool-12:) Investigating why 
> host 4 has disconnected with event PingTimeout
> WARN  [agent.manager.AgentManagerImpl] (AgentTaskPool-12:) Unsupported 
> Command: Unsupported command issued:com.cloud.agent.api.CheckHealthCommand.  
> Are you sure you got the right type of server?
> WARN  [agent.manager.AgentManagerImpl] (AgentTaskPool-12:) Agent state cannot 
> be determined, do nothing
> INFO  [cloud.ha.HighAvailabilityManagerImpl] (HA-2:) checking health of usage 
> server
> INFO  [agent.manager.AgentMonitor] (Thread-8:) Found the following agents 
> behind on ping: [4]
> INFO  [agent.manager.AgentManagerImpl] (AgentTaskPool-13:) Investigating why 
> host 4 has disconnected with event PingTimeout
> WARN  [agent.manager.AgentManagerImpl] (AgentTaskPool-13:) Unsupported 
> Command: Unsupported command issued:com.cloud.agent.api.CheckHealthCommand.  
> Are you sure you got the right type of server?
> WARN  [agent.manager.AgentManagerImpl] (AgentTaskPool-13:) Agent state cannot 
> be determined, do nothing
> INFO  [agent.manager.AgentMonitor] (Thread-8:) Found the following agents 
> behind on ping: [4]
> INFO  [agent.manager.AgentManagerImpl] (AgentTaskPool-14:) Investigating why 
> host 4 has disconnected with event PingTimeout
> WARN  [agent.manager.AgentManagerImpl] (AgentTaskPool-14:) Unsupported 
> Command: Unsupported command issued:com.cloud.agent.api.CheckHealthCommand.  
> Are you sure you got the right type of server?
> WARN  [agent.manager.AgentManagerImpl] (AgentTaskPool-14:) Agent state cannot 
> be determined, do nothing
> Attaching the screen shot to show the listNetworks API response time captured 
> in firebug.

--
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

Reply via email to