[jira] [Updated] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token

["Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>]

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

Vinod Kumar Vavilapalli updated YARN-4183:
------------------------------------------
    Fix Version/s:     (was: 2.7.2)
                       (was: 2.8.0)
                       (was: 3.0.0)

bq. All of this needs more work, so unless I hear strongly otherwise I am going to revert this patch in the interest of 2.7.2's progress.
Seeing no No's, reverted this for the sake of 2.7.2.

> Enabling generic application history forces every job to get a timeline service delegation token
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4183
>                 URL: https://issues.apache.org/jira/browse/YARN-4183
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.1
>            Reporter: Mit Desai
>            Assignee: Mit Desai
>         Attachments: YARN-4183.1.patch
>
>
> When enabling just the Generic History Server and not the timeline server, the system metrics publisher will not publish the events to the timeline store as it checks if the timeline server and system metrics publisher are enabled before creating a timeline client.
> To make it work, if the timeline service flag is turned on, it will force every yarn application to get a delegation token.
> Instead of checking if timeline service is enabled, we should be checking if application history server is enabled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)