question Re: Sqoop Import Job Stuck at 0% with Missing resource-types.xml in Cloudera CDH in Support Questions

Sqoop Import Job Stuck at 0% with Missing resource-types.xml in Cloudera CDH

helk — Fri, 06 Dec 2024 14:25:56 GMT

Hi all,

When running a Sqoop import , the job gets stuck at INFO mapreduce.Job: map 0% reduce 0%, and the process does not progress further. Additionally, the following error message appears in the logs:

INFO conf.Configuration: resource-types.xml not found.
INFO resource.ResourceUtils: Unable to find 'resource-types.xml'.

Despite this error, there are still plenty of available resources in the cluster, so resource allocation should not be the issue.

How can I resolve the "resource-types.xml not found" issue?
Where should the resource-types.xml file be placed in CDP?

Re: Sqoop Import Job Stuck at 0% with Missing resource-types.xml in Cloudera CDH

helk — Sun, 08 Dec 2024 11:45:05 GMT

any ideas please !

Re: Sqoop Import Job Stuck at 0% with Missing resource-types.xml in Cloudera CDH

VidyaSargur — Wed, 11 Dec 2024 09:20:59 GMT

@helk Welcome to our community! To help you get the best possible answer, I have tagged our Sqoop experts @M_Rahi @JoseManuel @Saurabhatiyal who may be able to assist you further.

Please feel free to provide any additional information or details about your query. We hope that you will find a satisfactory solution to your question.

Re: Sqoop Import Job Stuck at 0% with Missing resource-types.xml in Cloudera CDH

JoseManuel — Wed, 11 Dec 2024 14:33:29 GMT

Hello,

These are NOT ERRORS:

INFO conf.Configuration: resource-types.xml not found. INFO resource.ResourceUtils: Unable to find 'resource-types.xml'.

As for this:

INFO mapreduce.Job: map 0% reduce 0%

How many mappers were specified for the IMPORT?
Try locating the running containers in YARN and take a few JSTACKs to find out if the mapper is stuck waiting from your source database, if so make sure there are no firewall/network rules preventing the flow of data.
Are you able to execute SQOOP EVAL on the source DB?
If so, try using options:

-jt local -m 1 --verbose

If the job completes, that would confirm a communication issue from your NodeManagers to the source DB