chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerome Boulon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-440) Custom processor classes not detected unless added to chukwa-core jar
Date Wed, 23 Dec 2009 17:44:29 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794123#action_12794123
] 

Jerome Boulon commented on CHUKWA-440:
--------------------------------------

It's an Hadoop problem. Hadoop is running the demux using several machines so the jar needs
to be available on all data nodes.
The way to use more than one jar is to add the -libjars option to your hadoop command, you
can try that for Demux.
Let me know if it's working or not.


> Custom processor classes not detected unless added to chukwa-core jar
> ---------------------------------------------------------------------
>
>                 Key: CHUKWA-440
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-440
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: Data Processors
>            Reporter: Bill Graham
>
> http://wiki.apache.org/hadoop/DemuxModification
> After implementing a custom parser as shown in the wiki link above and mapping it to
a data type in chukwa-demux.xml, there's no easy way to register the class so it gets included
in the job that's submitted to the hadoop cluster. I've added my jar containing the class
to the lib/ directory of the chukwa data processor install and verified that it's in the classapath,
but it's not submitted with the Hadoop job. On the Hadoop cluster ClassNotFoundExceptions
are thrown in my mapper.
> The only way I've been able to make this work is to do the following: 
> 1. put my class in the package org.apache.hadoop.chukwa.extraction.demux.processor.mapper
> 2. then manually add that class to the chukwa-core-0.3.0.jar that is on my data processor
> Instead, the class should be detected from whatever jar it lives in that's in the demux
class path, regardless of the package it lives in.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message