[
https://issues.apache.org/jira/browse/CHUKWA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720425#action_12720425
]
Jerome Boulon commented on CHUKWA-302:
--------------------------------------
-1 in order to get an agreement not on the patch itself:
What about if I'm running a bunch of web servers and I just want to collect the
HTTP logs and I don't have hadoop at all?
I understand that for the backend (processing pipeline) we don't want to
include hadoop jars since we know that there's one already available somewhere
but why do we assume that hadoop is installed on the system that we want to
monitor?
That bring back the packaging issue for the processing pipeline and the agent.
Ps: this is a corner case that is not included in CHUKWA-297
> Chukwa Agent unable to start up and running
> -------------------------------------------
>
> Key: CHUKWA-302
> URL: https://issues.apache.org/jira/browse/CHUKWA-302
> Project: Hadoop Chukwa
> Issue Type: Bug
> Components: data collection
> Affects Versions: 0.2.0
> Environment: Redhat EL 5.1, Java 6
> Reporter: Eric Yang
> Priority: Blocker
> Fix For: 0.2.0
>
> Attachments: CHUKWA-302.patch
>
>
> agent.sh is hard coded with HADOOP_20_JAR. However, this may not reflect the
> correct running version of the hadoop library. agent.sh should obey
> HADOOP_JAR variable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
