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

Haibo Chen commented on YARN-8338:
----------------------------------

[~jlowe] [~vinodkv], I did not understand who else was depending on objenesis 
2.1, so wanted to avoid the accidental upgrade of objenesis. The upgrade of 
de.ruedigermoeller:fst would have upgraded objenesis from 2.1 to 2.5.1 at the 
time, without the exclusion of objenesis from fst. Based on [this fst 
comment|https://github.com/RuedigerMoeller/fast-serialization/blob/aceaad0075b2e1ef796597a1098aeb39fbea7fc9/pom.xml#L141],
 I assumed it was safe to do so, and there was not issue found in my test (as 
Jason noted, a dependency of mockito-all previously brought in objensis 
transitively).

[This 
comment|https://github.com/RuedigerMoeller/fast-serialization/blob/aceaad0075b2e1ef796597a1098aeb39fbea7fc9/pom.xml#L141]
 says that if android is not used, we don't need objenesis. It'd be nice if we 
can remove such runtime dependency from application history service, and let 
hadoop-aws to choose whichever verion of objenesis it needs.

> TimelineService V1.5 doesn't come up after HADOOP-15406
> -------------------------------------------------------
>
>                 Key: YARN-8338
>                 URL: https://issues.apache.org/jira/browse/YARN-8338
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Critical
>         Attachments: YARN-8338.txt
>
>
> TimelineService V1.5 fails with the following:
> {code}
> java.lang.NoClassDefFoundError: org/objenesis/Objenesis
>       at 
> org.apache.hadoop.yarn.server.timeline.RollingLevelDBTimelineStore.<clinit>(RollingLevelDBTimelineStore.java:174)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to