tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAJO-83) Handling the exception caused by integration test without the jvm option '-Dtajo.test=true'
Date Fri, 12 Jul 2013 01:24:46 GMT
Hyunsik Choi created TAJO-83:
--------------------------------

             Summary: Handling the exception caused by integration test without the jvm option
'-Dtajo.test=true'
                 Key: TAJO-83
                 URL: https://issues.apache.org/jira/browse/TAJO-83
             Project: Tajo
          Issue Type: Improvement
            Reporter: Hyunsik Choi
             Fix For: 0.2-incubating


When an integration test is performed without the jvm option '-Dtajo.test=TRUE', ContainerLauncherImpl
causes the following exception because it cannot obtain necessary environment variables and
class paths.
{noformat}
2013-07-12 10:06:33,406 INFO  master.TaskRunnerLauncherImpl (TaskRunnerLauncherImpl.java:createContainerLaunchContext(523))
- Completed setting up TaskRunner command ${JAVA_HOME}/bin/java -Xmx2000m org.apache.tajo.worker.TaskRunner
192.168.0.117 50101 sq_1373591183665_0001_000001_01 192.168.0.117:53741 container_1373591183665_0001_01_000001
1><LOG_DIR>/stdout 2><LOG_DIR>/stderr 
2013-07-12 10:06:33,410 ERROR master.TaskRunnerLauncherImpl (TaskRunnerLauncherImpl.java:launch(419))
- Container launch failed for container_1373591183665_0001_01_000001 : java.lang.NullPointerException
	at org.apache.hadoop.yarn.proto.YarnProtos$StringStringMapProto$Builder.setValue(YarnProtos.java:24622)
	at org.apache.hadoop.yarn.api.records.impl.pb.ContainerLaunchContextPBImpl$3$1.next(ContainerLaunchContextPBImpl.java:420)
	at org.apache.hadoop.yarn.api.records.impl.pb.ContainerLaunchContextPBImpl$3$1.next(ContainerLaunchContextPBImpl.java:408)
	at com.google.protobuf.AbstractMessageLite$Builder.addAll(AbstractMessageLite.java:310)
	at org.apache.hadoop.yarn.proto.YarnProtos$ContainerLaunchContextProto$Builder.addAllEnvironment(YarnProtos.java:21993)
	at org.apache.hadoop.yarn.api.records.impl.pb.ContainerLaunchContextPBImpl.addEnvToProto(ContainerLaunchContextPBImpl.java:431)
	at org.apache.hadoop.yarn.api.records.impl.pb.ContainerLaunchContextPBImpl.mergeLocalToBuilder(ContainerLaunchContextPBImpl.java:99)
	at org.apache.hadoop.yarn.api.records.impl.pb.ContainerLaunchContextPBImpl.mergeLocalToProto(ContainerLaunchContextPBImpl.java:112)
	at org.apache.hadoop.yarn.api.records.impl.pb.ContainerLaunchContextPBImpl.getProto(ContainerLaunchContextPBImpl.java:72)
	at org.apache.hadoop.yarn.api.protocolrecords.impl.pb.StartContainerRequestPBImpl.convertToProtoFormat(StartContainerRequestPBImpl.java:104)
	at org.apache.hadoop.yarn.api.protocolrecords.impl.pb.StartContainerRequestPBImpl.mergeLocalToBuilder(StartContainerRequestPBImpl.java:58)
	at org.apache.hadoop.yarn.api.protocolrecords.impl.pb.StartContainerRequestPBImpl.mergeLocalToProto(StartContainerRequestPBImpl.java:65)
	at org.apache.hadoop.yarn.api.protocolrecords.impl.pb.StartContainerRequestPBImpl.getProto(StartContainerRequestPBImpl.java:50)
	at org.apache.hadoop.yarn.api.impl.pb.client.ContainerManagerPBClientImpl.startContainer(ContainerManagerPBClientImpl.java:103)
	at org.apache.tajo.master.TaskRunnerLauncherImpl$ContainerProxy.launch(TaskRunnerLauncherImpl.java:387)
	at org.apache.tajo.master.TaskRunnerLauncherImpl$LaunchRunner.run(TaskRunnerLauncherImpl.java:130)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)
{noformat}

Developers who do not read HowToContribution (http://wiki.apache.org/tajo/HowToContribute)
in detail can be confused by this exception. We need to improve this part to print more kind
message for newcomers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message