You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2014/10/12 18:43:33 UTC
[jira] [Commented] (ACCUMULO-3230) MR/Yarn job submission fails
using `accumulo` with timeline client enabled
[ 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)