You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2015/02/25 18:19:05 UTC
[jira] [Commented] (AMBARI-9800) 400-node cluster: Hosts page stuck
in loading state
[ https://issues.apache.org/jira/browse/AMBARI-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336781#comment-14336781 ]
Andrii Tkach commented on AMBARI-9800:
--------------------------------------
+1 for the patch.
> 400-node cluster: Hosts page stuck in loading state
> ---------------------------------------------------
>
> Key: AMBARI-9800
> URL: https://issues.apache.org/jira/browse/AMBARI-9800
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9800.patch, AMBARI-9800_branch_2.0.patch
>
>
> Go to hosts page.
> After loading hosts next request sent to server: /api/v1/clusters/c1?fields=Clusters/health_report,Clusters/total_hosts,alerts_summary_hosts&minimal_response=true
> but it fails as "cancelled", UI sends request every 6 seconds, regardless whether previous was finished or not, so server can't response in time as if number of calls growing.
> UI should make next call only when previous finished, should apply this approach to all pollings in ambari web to guarantee performance on big cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)