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.

No AbstractFileSystem configured for scheme: sandbox.hortonworks.com

Highlighted

No AbstractFileSystem configured for scheme: sandbox.hortonworks.com

I try to start a simple workflow in Oozie using the Sandbox 2.3.2, but I get the following error in oozie.log:

SERVER[sandbox.hortonworks.com] PrivilegedActionException as:hdfs (auth:PROXY) via oozie (auth:SIMPLE) cause:org.apache.hadoop.fs.UnsupportedFileSystemException: fs.AbstractFileSystem.sandbox.hortonworks.com.impl=null: No AbstractFileSystem configured for scheme: sandbox.hortonworks.com

5 REPLIES 5
Highlighted

Re: No AbstractFileSystem configured for scheme: sandbox.hortonworks.com

Mentor

what is the value for namenodes property? Refer to this for example https://github.com/dbist/oozie/tree/master/apps

Look at shell example and see job.properties then look at workflow.xml

Highlighted

Re: No AbstractFileSystem configured for scheme: sandbox.hortonworks.com

Expert Contributor

@Nicola,

I'm assuming that you are submitting the oozie workflow using the command line.

Can you make sure that the job.properties as below:

nameNode=fs.defaultFS -> from HDFS config

jobTracker=yarn.resourcemanager.address - from Yarn config

oozie.use.system.libpath=true

oozie.wf.application.path=${nameNode}/PATH_TO_WORKFLOW_IN_HDFS.

Highlighted

Re: No AbstractFileSystem configured for scheme: sandbox.hortonworks.com

Mentor

@Nicola Marangoni my workflow.xml

<workflow-app xmlns="uri:oozie:workflow:0.4" name="shell-wf">
    <start to="shell-node"/>
    <action name="shell-node">
        <shell xmlns="uri:oozie:shell-action:0.2">
            <job-tracker>${jobTracker}</job-tracker>
            <name-node>${nameNode}</name-node>
            <configuration>
                <property>
                    <name>mapred.job.queue.name</name>
                    <value>${queueName}</value>
                </property>
            </configuration>
            <exec>script.sh</exec>
	    <file>scripts/script.sh</file> 	
           <!-- <argument>my_output=Hello Oozie</argument> -->
            <capture-output/>
        </shell>
        <ok to="end"/>
        <error to="fail"/>
    </action>
    <kill name="fail">
        <message>Shell action failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message>
    </kill>
    <kill name="fail-output">
        <message>Incorrect output, expected [Hello Oozie] but was [${wf:actionData('shell-node')['my_output']}]</message>
    </kill>
    <end name="end"/>
</workflow-app>
Highlighted

Re: No AbstractFileSystem configured for scheme: sandbox.hortonworks.com

Mentor

my example job.properties

nameNode=hdfs://sandbox.hortonworks.com:8020
jobTracker=sandbox.hortonworks.com:8050
queueName=defaultexamplesRoot=oozie
oozie.wf.application.path=${nameNode}/user/${user.name}/${examplesRoot}/apps/shell

					
				
			
			
				
			
			
			
			
			
			
			
		

Re: No AbstractFileSystem configured for scheme: sandbox.hortonworks.com

I have the following:

nameNode=hdfs://sandbox.hortonworks.com:8020
jobTracker=sandbox.hortonworks.com:8050
master=yarn-cluster
user.name=hdfs
queueName=spark
oozie.use.system.libpath=true
oozie.wf.application.path=hdfs://sandbox.hortonworks.com:8020/user/hdfs/spark-test

And:

<workflow-app xmlns='uri:oozie:workflow:0.5' name='SimpleSparkApp'>
    <start to='spark-node' />
    <action name='spark-node'>
        <spark xmlns="uri:oozie:spark-action:0.1">
            <job-tracker>sandbox.hortonworks.com:8050</job-tracker>
            <name-node>sandbox.hortonworks.com:8020</name-node>
            <master>yarn-cluster</master>
            <mode>cluster</mode>
            <name>Spark-Test</name>
            <class>de.david.spark.SimpleSparkApp</class>
            <jar>hdfs://sandbox.hortonworks.com:8020/user/hdfs/spark-test/lib/spark-test-0.0.1-SNAPSHOT.jar</jar>
        </spark>
        <ok to="end" />
        <error to="fail" />
    </action>
    <kill name="fail">
        <message>Workflow failed, error
            message[${wf:errorMessage(wf:lastErrorNode())}]
        </message>
    </kill>
    <end name='end' />
</workflow-app>

The same configuration works on another cluster. It seems that some where a variable with the name fs.AbstractFileSystem.sandbox.hortonworks.com.impl is defined. Is it a right interpretation?

Don't have an account?
Coming from Hortonworks? Activate your account here