[HDFS-14825] [Dynamometer] Workload doesn't start unless an absolute path of Mapper class given

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0
• Hadoop Flags: Reviewed
• Assignee: Takanobu Asanuma
• Reporter: Soya Miyoshi
• Created: 06/Sep/19 05:36
• Updated: 04/Dec/19 03:46
• Resolved: 04/Dec/19 02:30

Description

When starting a workload by start-workload.sh, unless an absolute path of Mapper is given, the workload doesn't start.

 

$ hadoop/tools/dynamometer/dynamometer-workload/bin/start-workload.sh - \
Dauditreplay.input-path=hdfs:///user/souya/input/audit  \
-Dauditreplay.output-path=hdfs:///user/souya/results/ \
-Dauditreplay.num-threads=50 -Dauditreplay.log-start-time.ms=5 \
-nn_uri hdfs://namenode_address:port/ \
-mapper_class_name AuditReplayMapper

results in

SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Exception in thread "main" java.lang.ClassNotFoundException: Class org.apache.hadoop.tools.dynamometer.workloadgenerator.AuditReplayMapper not found
	at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2572)
	at org.apache.hadoop.tools.dynamometer.workloadgenerator.WorkloadDriver.getMapperClass(WorkloadDriver.java:183)
	at org.apache.hadoop.tools.dynamometer.workloadgenerator.WorkloadDriver.run(WorkloadDriver.java:127)
	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
	at org.apache.hadoop.tools.dynamometer.workloadgenerator.WorkloadDriver.main(WorkloadDriver.java:172)

Issue Links

• links to: GitHub Pull Request #1693