Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Windows, downstream applications with long aggregate classpaths
Description
When a task is started on the tasktracker, it creates a small batch file to invoke java and runs that batch. Within the batch file, the invocation of Java currently has -classpath ${CLASSPATH} inline to the command. That line often exceeds 8000 characters. This is ok for most linux distributions because the line limit env variable is often set much higher than this. However, for Windows this cause cmd to abort execution. This surfaces in Hadoop as an unknown failure mode for the task.
I think the easiest and most natural way to fix this is to push the -classpath option into a config file to take the longest variable part of the line and put it somewhere that scales better.
Attachments
Attachments
Issue Links
- relates to
-
HADOOP-8079 Proposal for enhancements to Hadoop for Windows Server and Windows Azure development and runtime environments
- Resolved