[
https://issues.apache.org/jira/browse/AMBARI-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-4225:
--------------------------------
Description:
When starting/stopping components based on the Start/Stop Components buttons
that show up after service reconfiguration, it creates one request per
component (as shown in the Background Operations popup). This floods the
request history and the user cannot see what has been done prior. From the
user's standpoint, Start Components and Stop Components actions should each
show up as one request.
Also, this has major performance implications, since multiple requests cannot
be processed in parallel by the server (unlike tasks within a single request).
> Starting/Stopping components based on restart indicator floods request
> history and execution queue
> --------------------------------------------------------------------------------------------------
>
> Key: AMBARI-4225
> URL: https://issues.apache.org/jira/browse/AMBARI-4225
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.3
> Reporter: Yusaku Sako
> Assignee: Yusaku Sako
> Fix For: 1.4.3
>
>
> When starting/stopping components based on the Start/Stop Components buttons
> that show up after service reconfiguration, it creates one request per
> component (as shown in the Background Operations popup). This floods the
> request history and the user cannot see what has been done prior. From the
> user's standpoint, Start Components and Stop Components actions should each
> show up as one request.
> Also, this has major performance implications, since multiple requests cannot
> be processed in parallel by the server (unlike tasks within a single request).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
