MR2 can't run local jobs with -libjars command options which is a regression from MR1.
When run MR2 job with -jt local and -libjars, the job fails with java.io.FileNotFoundException: File does not exist: hdfs://XXXXXXXXXXXXXXX.jar.
But the same command is working in MR1.
I find the problem is
because when MR2 run local job using LocalJobRunner
from JobSubmitter, the JobSubmitter#jtFs is local filesystem,
So copyRemoteFiles will return from the middle of the function
because source and destination file system are same.
The following code at JobSubmitter.java
try to add the destination file to DistributedCache which introduce a bug for local job.
Because new Path(newPath.toUri().getPath()) will lose the filesystem information from newPath, the file added to DistributedCache will use the default Uri filesystem hdfs based on the following code. This causes the
FileNotFoundException when we access the file later at
Compare to the following MR1 code:
You will see why MR1 doesn't have this issue.
because it passes the local filesystem into DistributedCache#addFileToClassPath instead of using the default Uri filesystem hdfs.
Another incompatible change in MR2 is in LocalDistributedCacheManager#setup
Similar code from MR1 is at TaskDistributedCacheManager#makeCacheFiles
I think we don't need call remoteFS.resolvePath to get the class path and
We can use the class path from DistributedCache.getFileClassPaths directly.
Also p.toUri().getPath().toString() will remove the filesystem information(scheme) and only keySet of classpaths is used(ValueSet of classpaths is not used).
It is better to do the same in MR2 to maintain backward compatible with MR1.