You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Arpit Gupta (JIRA)" <ji...@apache.org> on 2014/07/21 23:26:40 UTC

[jira] [Created] (HDFS-6715) webhdfs wont fail over when it gets java.io.IOException: Namenode is in startup mode

Arpit Gupta created HDFS-6715:
---------------------------------

             Summary: webhdfs wont fail over when it gets java.io.IOException: Namenode is in startup mode
                 Key: HDFS-6715
                 URL: https://issues.apache.org/jira/browse/HDFS-6715
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: ha
    Affects Versions: 2.2.0
            Reporter: Arpit Gupta


Noticed in our HA testing when we run MR job with webhdfs file system we some times run into 

{code}
2014-04-17 05:08:06,346 INFO [AsyncDispatcher event handler] org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics report from attempt_1397710493213_0001_r_000008_0: Container killed by the ApplicationMaster.
Container killed on request. Exit code is 143
Container exited with a non-zero exit code 143

2014-04-17 05:08:10,205 ERROR [CommitterEvent Processor #1] org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler: Could not commit job
java.io.IOException: Namenode is in startup mode
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
{code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)