Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Oozie / HA - No failover

Highlighted

Oozie / HA - No failover

New Contributor

hi,

We are trying to determine how oozie determines the namenode. We are configured with 2: when #1 goes into standby, making #2 primary, oozie workflow jobs die: JA009: Operation category READ is not supported in state standby at org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87) at org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1872) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1306) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:3852)

because it is still trying to connection to #1. The rest of the system handle appears to handle the changing namenodes correctly. Where does oozie pull this information? hdfs-site.conf? That is appears correct. could there be additional parameters that would override this configuration?

Thanks.

2 REPLIES 2

Re: Oozie / HA - No failover

@Stephen knott

In your Oozie wf, you need to set the name node property to the name service of HDFS instead of one of the NN. This error probably means you point to one NN but this NN is not the active one anymore.

Hope this helps.

Re: Oozie / HA - No failover

Guru

more specifically, it's located in your job.properties :

namenode=hdfs://<nameservice>
Don't have an account?
Coming from Hortonworks? Activate your account here