My best guess would be that an older version of commons-codec is also on
the classpath for the running task. If you have access to the local-dirs
configured under YARN - you could find the application dir in the
local-dirs and see what exists in the classpath for a container.
Alternately, set
Thanks for your input. There are two weird points found:
- In my cluster (also the resources being localized for the tasks) there
are two versions; commons-codec-1.4.jar and commons-codec-1.7.jar. I
think commons-codec since version 1.4 shows be fine, but I still got the
exception
commons-codec contains the method since 1.4 - so those two versions of the
jar in the classpath should not cause issues.
Are there any custom jars which are loaded ? I'd look at any fat jars (Pig
for example) - to see if they're bundling commons-codec within them.
You could try this
