You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2014/03/17 16:35:44 UTC

[jira] [Resolved] (AMBARI-5089) Upgrade Issue with History Server in HDP 1.

     [ https://issues.apache.org/jira/browse/AMBARI-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Onischuk resolved AMBARI-5089.
-------------------------------------


committed to trunk

> Upgrade Issue with History Server in HDP 1.
> -------------------------------------------
>
>                 Key: AMBARI-5089
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5089
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-5089.patch
>
>
> Upgrade Issue with History Server in HDP 1.
> The following is the issue:
> With new HDP 1 work History Server is being treated as a separate component - earlier it was part of JobTracker start/stop/management. When users who are using HDP 1 and just upgrade Ambari they will not have a History Server component. This will mean that in MR there will nto be any History Server running. We need to find a way to make this seem less for the user. 
> Best would be add it to our DDL upgrade script where we add a new host componenet History Server on the same host as the JobTracker. 
> Feel free to evaluate and propose other solutions.



--
This message was sent by Atlassian JIRA
(v6.2#6252)