[
https://issues.apache.org/jira/browse/OOZIE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226506#comment-13226506
]
Alejandro Abdelnur commented on OOZIE-751:
------------------------------------------
Does your cluster have enough slots to run all those jobs concurrently?
Can you run your sqoop commands in parallel from the command line (from
different terminals)?
oozie uses as launcher job (MR job for 1 map task and 0 reduce job) to launch
the real job (the sqoop job in your case), you can see the job names being
oozie:launcher and oozie:action
> Sqoop jobs through oozie hangs if I try to load more than 1 table in parallel
> -----------------------------------------------------------------------------
>
> Key: OOZIE-751
> URL: https://issues.apache.org/jira/browse/OOZIE-751
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.2.0
> Environment: CentOs 5.0, hadoop-0.20.2, sqoop-1.3.0, oozie-2.3.2
> Reporter: Aman Preet Singh
> Attachments: how_3_oozie_jobs_look_in_jobtracker_ui.png, tasklog.htm,
> this_is_how_oozie_directory_structure_looks_in_hdfs.txt, workflow.xml
>
>
> I want to load data from SQL Server to HDFS and am using the sqoop action of
> Oozie as defined on page
> http://archive.cloudera.com/cdh/3/oozie-2.3.2-cdh3u3/DG_SqoopActionExtension.html.
>
> It works when I try to copy 1 table but when I try to copy more than 1 table
> is parallel then the job just hangs. I don't see any errors anywhere in the
> logs.
> - I have confirmed that there are no deadlocks on the database side.
> - I have confirmed that if I try to load multiple table in parallel using
> sqoop command line then it works fine
> It looks like there is something in oozie sqoop action.
> One more thing that I noticed is that there are 3 oozie jobs running in the
> oozie console but 6 jobs are shown in Jobtracker UI (please see screenshot
> attached). Not sure why that is.
> The workflow.xml file, tasktracker logs for the task and how oozie directory
> looks on HDFS is attached.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
