Support Questions

Find answers, ask questions, and share your expertise

Oozie Sqoop Job gets stuck at 95%

New Contributor

Am trying to run a sqoop job on oozie but it's getting stuck at 95% but the same sqoop command runs perfectly on the command line.

I am running HDP 2.6.2

The following is my workflow xml, hive xml and job properties

Workflow xml

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<workflow-app xmlns="uri:oozie:workflow:0.5" name="Sqoop_Import_105">
    <start to="sqoop_ext_105"/>
    <action name="sqoop_ext_105">
        <sqoop xmlns="uri:oozie:sqoop-action:0.4">
                <delete path="/user/admin/Data/Users/Extract"/>
                <mkdir path="/user/admin/Data/Users/Extract"/>
            <command>import --connect jdbc:mysql://xxxxxx/xx --username xxxxx --password xxxxxx --table users --direct --split-by id --target-dir /user/admin/Data/Test</command>
        <ok to="end"/>
        <error to="kill"/>
    <kill name="kill">
    <end name="end"/>

hive xml

<configuration supports_final="true">






job properties


Attached is where the job gets stuck


Kindly assist


The sqoop commands from command line and the ones that will work to completion in oozie are going to be slightly different. This difference is based on container enviroment, paths, and permissions.

The only way to trouble shoot is to go into YARN UI, and click deep into the log for the containers and the application failure(s). You are specifically looking for the logs of the failed container. Be careful as there are several higher level of logs that are not always going to show the errors. You will most likely be looking in every possible place.

For my oozie / sqoop job the click through path is:

1. From workflow tab, click into the job.

2. Inspect the log tabs here.

3. Follow link to the Job into the Yarn Resource UI.

2. Next find the container that executed the job(s) and click on the link to those Logs. This can be 1 or 2 pages to click through so be sure to inspect all links into sub pages.

3. Inspect the log output at the deepest levels for additional information and usually the error you need to solve.

Once you have the actual failures, it is usually descriptive enough to direct some adjustment in the workflow. Retry the application and repeat until resolved.

Good luck, and if this answer helps, please choose ACCEPT.