Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

sqoop deadlock on basic job / stuck on booting

avatar
Explorer

Hi,

 

I'm trying to do a basic job in sqoop using sqoop-import to a sybase db

sqoop import --connect jdbc:sybase:Tds:syserver:5000/mydb?ServiceName=master --username user --password password --driver com.sybase.jdbc4.jdbc.SybDriver --query "SELECT * FROM point_vente WHERE \$CONDITIONS" --split-by id --target-dir /user/sybase/test.csv

 

I've correctly added the JAR file required for sybase and I'm able to use:

  • sqoop list-tables
  • sqoop list-databases
  • and I can use the same query above with sqoop eval and have correct results.

BUT when launched the above job, it stucks, the jobs is blocked on booting. I only have this for debugging the deadlock:

 

2016-12-23 13:21:08,222 DEBUG driver.JobManager [org.apache.sqoop.driver.JobManager$UpdateThread.run(JobManager.java:671)] Updating running submissions
2016-12-23 13:21:08,223 DEBUG repository.JdbcRepositoryTransaction [org.apache.sqoop.repository.JdbcRepositoryTransaction.begin(JdbcRepositoryTransaction.java:74)] Tx count-begin: 1, rollback: false
2016-12-23 13:21:08,223 DEBUG repository.JdbcRepositoryTransaction [org.apache.sqoop.repository.JdbcRepositoryTransaction.commit(JdbcRepositoryTransaction.java:85)] Tx count-commit: 1, rollback: false
2016-12-23 13:21:08,223 DEBUG repository.JdbcRepositoryTransaction [org.apache.sqoop.repository.JdbcRepositoryTransaction.close(JdbcRepositoryTransaction.java:104)] Tx count-close: 0, rollback: false
2016-12-23 13:21:08,224 INFO  repository.JdbcRepositoryTransaction [org.apache.sqoop.repository.JdbcRepositoryTransaction.close(JdbcRepositoryTransaction.java:112)] Attempting transaction commit

I've tried with sqoop2 using hue, same problem.

 

Note : I'm running on the cloudera quickstart docker

 

 

 

1 ACCEPTED SOLUTION

avatar
Explorer

The problem was solved by re-adding the jar file (maybe corrupted jars) and restart the cluster

View solution in original post

1 REPLY 1

avatar
Explorer

The problem was solved by re-adding the jar file (maybe corrupted jars) and restart the cluster