You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2014/01/04 01:24:56 UTC
[jira] [Commented] (AMBARI-4225) Starting/Stopping components based
on restart indicator floods request history and execution queue
[ https://issues.apache.org/jira/browse/AMBARI-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862074#comment-13862074 ]
Yusaku Sako commented on AMBARI-4225:
-------------------------------------
Fix:
1. Service > Restart > Start Components. Creates two requests: "Start Components" and "Update Clients". This starts all the stale non-client host components and updates the stale client host components for the service.
2. Service > Restart > Stop Components. Creates one request: "Stop Components". This stops all the stale non-client host components for the service.
3. Host > Restart > Start Components. Creates two requests: "Start Components" and "Update Clients". This starts all the stale non-client host components and updates the stale client host components on the host.
4. Host > Request >Stop Components. Creates one request: "Stop Components". This stops all the stale non-client host components on the host.
> 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)