Support Questions

Find answers, ask questions, and share your expertise

ImportTsv Failing with Exit Code 1 and SLF4J Logger Issue in HBase MapReduce Job

avatar
Contributor

Dear Cloudera Support Team,

I am experiencing an issue when running the ImportTsv command in HBase using the following command:
hbase org.apache.hadoop.hbase.mapreduce.ImportTsv -Dimporttsv.separator='\t' -Dimporttsv.columns='HBASE_ROW_KEY,cf:gender,cf:age,cf:income,cf:exp' Customers /hbase/data.txt
The job is failing with the following error message:

2024-10-03T15:00:41,530 INFO [main] mapreduce.Job: Running job: job_1727859616916_0004
2024-10-03T15:00:50,594 INFO [main] mapreduce.Job: Job job_1727859616916_0004 running in uber mode : false
2024-10-03T15:00:50,597 INFO [main] mapreduce.Job: map 0% reduce 0%
2024-10-03T15:00:50,616 INFO [main] mapreduce.Job: 9616916_0004_02_000001
Exit code: 1

[2024-10-03 15:00:49.597]Container exited with a non-zero exit code 1. Error file: prelaunch.err.
Last 4096 bytes of prelaunch.err :
Last 4096 bytes of stderr :
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

For more detailed output, I have checked the logs on the application tracking page as well:
http://dc1-apache-hbase.mobitel.lk:8088/cluster/app/application_1727859616916_0004

here is the above mentioned (application_1727859616916_0004) result.

User:Name:Application Type:Application Tags:Application Priority:YarnApplicationState:Queue:FinalStatus Reported by AM:Started:Launched:Finished:Elapsed:Tracking URL:Log Aggregation Status:Application Timeout (Remaining Time):Diagnostics:Unmanaged Application:Application Node Label expression:AM container Node Label expression:

super
importtsv_Customers
MAPREDUCE
 
0 (Higher Integer value indicates higher priority)
FAILED
default
FAILED
Thu Oct 03 15:00:41 +0530 2024
Thu Oct 03 15:00:42 +0530 2024
Thu Oct 03 15:00:49 +0530 2024
8sec
History
DISABLED
Unlimited

Application application_1727859616916_0004 failed 2 times due to AM Container for appattempt_1727859616916_0004_000002 exited with exitCode: 1

Failing this attempt.Diagnostics: [2024-10-03 15:00:49.594]Exception from container-launch.

Container id: container_1727859616916_0004_02_000001

Exit code: 1

[2024-10-03 15:00:49.597]Container exited with a non-zero exit code 1. Error file: prelaunch.err.

Last 4096 bytes of prelaunch.err :

Last 4096 bytes of stderr :

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

[2024-10-03 15:00:49.598]Container exited with a non-zero exit code 1. Error file: prelaunch.err.

Last 4096 bytes of prelaunch.err :

Last 4096 bytes of stderr :

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

For more detailed output, check the application tracking page: http://dc1-apache-hbase.mobitel.lk:8088/cluster/app/application_1727859616916_0004 Then click on links to logs of each attempt.

. Failing the application.

false
<Not set>
<DEFAULT_PARTITION>

 

Could you please assist in resolving this issue?

Thank you for your support.



1 REPLY 1

avatar
Community Manager

Hi! @shubham_sharma @aquilodran @Anandh_S Do you have any insights here? Thanks


Regards,

Diana Torres,
Senior Community Moderator


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community: