accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3230) MR/Yarn job submission fails using `accumulo` with timeline client enabled
Date Sun, 12 Oct 2014 16:43:33 GMT

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

Mike Drob commented on ACCUMULO-3230:
-------------------------------------

Doesn't Hadoop have a version of Jersey that it includes? If we include a version of Jersey,
does that open us up to potential incompatibilities with user code that relies on it?

> MR/Yarn job submission fails using `accumulo` with timeline client enabled
> --------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3230
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3230
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.2, 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.5.3, 1.6.2, 1.7.0
>
>
> The [timeline server|http://hadoop.apache.org/docs/r2.4.0/hadoop-yarn/hadoop-yarn-site/TimelineServer.html]
is a feature that allows for storage and retrieval of application timing information. Submitting
a mapreduce task has been instrumented to use this new feature, when enabled.
> To communicate with the server, the TimelineClient uses Jersey. This causes direct failures
in multiple randomwalk modules, but is generally applicable to any code run using the `accumulo`
command.
> Including the jersey libs to the general classpath should be harmless and prevent future
classpath issues.



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

Mime
View raw message