ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-1628) Tasktracker remains in STARTING state preventing Ambari to display proper status.
Date Wed, 13 Mar 2013 20:06:13 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601569#comment-13601569
] 

Sumit Mohanty commented on AMBARI-1628:
---------------------------------------

Added two patches - one for 1.2.2 and one for master. The patch for 1.2.2 has an additional
fix for unit test failures in AmbariMetaInfoTest.
                
> Tasktracker remains in STARTING state preventing Ambari to display proper status.
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-1628
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1628
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.2.2
>
>         Attachments: AMBARI-1628-1.2.2.patch, AMBARI-1628-master.patch
>
>
> If agent restarts prior to sending a response to START/STOP command request (after successful
start/stop at the host) then the state of the host component may not transition out of STARTING/STOPPING.
When the agent restarts it will start sending heart-beat with the correct component state
as STARTED/INSTALLED which will not be processed by the server. Heartbeat handler should reflect
the state based on the heart-beat.

--
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

Mime
View raw message