hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (YARN-3774) ZKRMStateStore should use CuratorOp when we upgrade to Curator 3
Date Mon, 24 Apr 2017 23:36:04 GMT

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

Robert Kanter reassigned YARN-3774:
-----------------------------------

            Assignee:     (was: Robert Kanter)
    Target Version/s:   (was: 3.0.0-alpha3)
            Priority: Minor  (was: Critical)
             Summary: ZKRMStateStore should use CuratorOp when we upgrade to Curator 3  (was:
ZKRMStateStore should use CuratorOp)

That seems reasonable.  I've updated the JIRA.

> ZKRMStateStore should use CuratorOp when we upgrade to Curator 3
> ----------------------------------------------------------------
>
>                 Key: YARN-3774
>                 URL: https://issues.apache.org/jira/browse/YARN-3774
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.8.0
>            Reporter: Karthik Kambatla
>            Priority: Minor
>         Attachments: YARN-3774.001.patch
>
>
> 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. 
> Curator is considering shading guava through CURATOR-200. In Hadoop 3, we should upgrade
to the next Curator version.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message