You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Myroslav Papirkovskyi (JIRA)" <ji...@apache.org> on 2017/03/29 16:09:41 UTC
[jira] [Commented] (AMBARI-20590) Ensure that result of start/stop
command is not temporarily overwritten by status commands
[ https://issues.apache.org/jira/browse/AMBARI-20590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947410#comment-15947410 ]
Myroslav Papirkovskyi commented on AMBARI-20590:
------------------------------------------------
Fix is mostly workaround to prevent executing status command for roles which has another task in progress.
Approach will probably change in Async Events and smart agent implementation
> Ensure that result of start/stop command is not temporarily overwritten by status commands
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-20590
> URL: https://issues.apache.org/jira/browse/AMBARI-20590
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Dhanya Balasundaran
> Assignee: Myroslav Papirkovskyi
> Priority: Critical
> Fix For: 3.0.0
>
>
> In case of unhappy timing start/stop task status report can be overridden by report of status command sent before task finish.
> This can result in temporary incorrect status until next status command report
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)