[
https://issues.apache.org/jira/browse/FLUME-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302669#comment-15302669
]
Mike Percy commented on FLUME-2913:
-----------------------------------
Hi [~bessbd], thanks for the patch. It looks like this patch primarily removes
exclusion of slf4j jars from the hadoop and hbase classpaths. Did you verify
whether including multiple versions of slf4j api / log4j connectors doesn't
cause a problem? Or do you have any explanation about this? From my
recollection (a hazy one, admittedly) that used to cause slf4j to refuse to
function.
Thanks,
Mike
> Flume classpath too long
> ------------------------
>
> Key: FLUME-2913
> URL: https://issues.apache.org/jira/browse/FLUME-2913
> Project: Flume
> Issue Type: Bug
> Reporter: Bessenyei Balázs Donát
> Assignee: Bessenyei Balázs Donát
> Attachments: FLUME-2913.patch
>
>
> Starting Flume generates the FLUME_CLASSPATH variable dynamically, adding
> jars one by one.
> In some cases, the classpath can grow too long, sometimes exceeding ARG_MAX,
> maximum length of arguments for a new process (
> http://www.in-ulm.de/~mascheck/various/argmax/ )
> Thus, being unable to start Flume:
> flume-ng/bin/flume-ng: line 239: /usr/java/jdk1.7.0_67/bin/java: Argument
> list too long
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
