You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/04/13 00:08:17 UTC

[jira] [Commented] (AMBARI-1919) JobTracker History Server failed to come up on 1.3.0 stack and the request for service stall is stalled

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

Sumit Mohanty commented on AMBARI-1919:
---------------------------------------

It seems that BE aborts the tasks, they get recorded in the DB but the API returns stale data showing the the tasks are pending. This is because the DB is updated under the cover and DAO entities are not updated.
                
> JobTracker History Server failed to come up on 1.3.0 stack and the request for service stall is stalled
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-1919
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1919
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.3.0
>
>
> Attempted to install a cluster with 1.3.0 stack.
> Service install was all green, but JobTracker History Server failed to come up.
> The request for the service start is stalled, with no tasks in QUEUED or IN_PROGRESS state, but with some tasks in PENDING state.

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