Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
0.9.0, 0.9.1, 0.9.1u1, 0.9.2
-
None
-
None
Description
The compression codec (FLUME-132) was finding codec's that weren't necessarily in flume's class path.
In this particular case the LZO algorithm jar was in the hadoop classpath but not in flume's. When flume asked for codecs, it failed to find the lzo codec and the collector then failed.
A work around a was to copy the lzo jar into flume's lib dir. Ideally, the "missing" codec would be a recoverable warning, or any hadoop jars would be added to flume's jar path. The latter may cause on jar conflict pain however.
Attachments
Issue Links
- relates to
-
FLUME-474 flume executable doesn't support extending java.library.path with flume-env.sh
- Closed