I don't think this has something to do with dependencies or libraries.
It seems you need to configure the 'inputCharset' property for your source
to match the expected character set for the input files on those systems.
The default used by Flume is UTF-8 and if the input file is not in the
expected character set, then when a sequence of input units that are not
well-formed are encountered or when the code encounters a sequence of input
units that denote a character that cannot be represented in the output
charset then we have a problem.
I think you should find out what the character set for those systems are
and try to make them match to avoid the problem.
If you include the operating systems these agents are running it might be
easier to guess which character set it is.
I am guessing you are running a Linux distro based on your file paths but
it could be Mac OS X.
*Author and Instructor for the Upcoming Book and Lecture Series*
*Massive Log Data Aggregation, Processing, Searching and Visualization with
Open Source Software*
On 18 July 2013 05:48, Jagadish Bihani <[EMAIL PROTECTED]> wrote:
> I am using spooling directory source with apache flume 1.4.0 and having
> the problem
> that *same configuration works on some machines and doesn't work on some
> Configuration used to work with flume 1.3.1. (Only the properties related
> to deserializer are changed).
> *Configuration is:*
> agent.sources.spooler.type = spooldir
> agent.sources.spooler.spoolDir = /TRACKING_TSV_FILES/tracking_backup_flume
> agent.sources.spooler.batchSize = 10000
> agent.sources.spooler.channels = fileChannel
> agent.sources.spooler.spooldir.deserializer= LINE
> agent.sources.spooler.spooldir.deserializer.maxLineLength = 20000
> *Exception stack trace is: **
> *java.nio.charset.MalformedInputException: Input length = 1
> at java.nio.charset.CoderResult.throwException(CoderResult.java:260)
> Is there any software/libraries dependency for it to work?