Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
The behavior of mapred.cache.files and mapred.cache.archives is different during localization in the following way:
If a jar file is added to mapred.cache.files, it will be localized under TaskTracker under a unique path.
If a jar file is added to mapred.cache.archives, it will be localized under a unique path in a directory named the jar file name, and will be unarchived under the same directory.
If same jar file is passed for both the configurations, the behavior undefined. Thus the job submission should fail.
Currently, since distributed cache processes files before archives, the jar file will be just localized and not unarchived.
Attachments
Attachments
Issue Links
- is duplicated by
-
MAPREDUCE-1709 mapred.cache.archives is not creating links for long path names
- Resolved