hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsuyoshi Ozawa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3774) ZKRMStateStore should use Curator 3.0 and avail CuratorOp
Date Tue, 09 Jun 2015 19:01:01 GMT

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

Tsuyoshi Ozawa commented on YARN-3774:

FYI: http://curator.apache.org/dependencies.html

Curator 2.7.1 also depends on Guava 16.0.1 though Hadoop depends on Guava 11.0.2. IIUC, we
have a possibility to face method missing error at runtime when we use specific features which
is available only with Guava 16.0.1. 
Steve describes what happens with upgrading Curator version on HADOOP-11102.

We have a chance to use maven-jarjar-plugin to avoid conflicts about Guava when we deal with

> ZKRMStateStore should use Curator 3.0 and avail CuratorOp
> ---------------------------------------------------------
>                 Key: YARN-3774
>                 URL: https://issues.apache.org/jira/browse/YARN-3774
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.8.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Blocker
> YARN-2716 changes ZKRMStateStore to use Curator. Transactions added there are somewhat
involved, and could be improved using CuratorOp introduced in Curator 3.0. Hadoop 3.0.0 would
be a good time to upgrade the Curator version and make this change. 

This message was sent by Atlassian JIRA

View raw message