You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2013/07/18 01:06:48 UTC
[jira] [Commented] (AMBARI-2670) Start button not available for
various components within 10 sec after stop operation finishes
[ https://issues.apache.org/jira/browse/AMBARI-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711774#comment-13711774 ]
Srimanth Gunturi commented on AMBARI-2670:
------------------------------------------
+1 for patch.
> Start button not available for various components within 10 sec after stop operation finishes
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-2670
> URL: https://issues.apache.org/jira/browse/AMBARI-2670
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.2.5
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 1.2.5
>
> Attachments: AMBARI-2670.patch
>
>
> Steps to reproduce:
> 1. Stop a component.
> 2. Wait for the corresponding BG operation to finish.
> Result:
> "Start" button isn't available for the component within 10 seconds since stop operation finished in UI. It appears later.
> This happens cuz of update interval, it is set to 15 seconds (App.contentUpdateInterval), that`s why in some moments it can take up to 15 sec to update components status, after request is done.
> Solution: Create a seperate update interval specialy for updating host components. In config.js we even have App.componentsUpdateInterval = 6000; But this value was not used anywhere in code till now.
--
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