Affects Version/s: None
Fix Version/s: None
We recently found that when -libjar specified jars on the same remote FS, jars will not be properly added to classpath.
The reason is
MAPREDUCE-6719 added the wildcard functionality, but the follow logic assumes files are all placed under job's submission directory. (Inside JobResourceUploader)
However, in the same method, specified resources will be only uploaded when two FSes are different, see copyRemoteFiles:
Workaround of this issue is pass:
mapreduce.client.libjars.wildcard = false.
When the MR job got launched.
Example commandline to reproduce this issue is: