Re: MySQL 4.1.22 Sqoop Connector

[Cody Krietemeyer]

Hello Alexander,

Neither c/J 3.1 or c/J 5.0 worked to any extent. Both gave an immediate error when trying to issue the Sqoop job.

Our current testing has been using c/J 5.1.45 and c/J 5.1.8 (which according to the MySQL 4.1 Reference Manual is the preferred connector). Using either of these versions, it looks like we are able to make a connection to the database, but the connection is not being accepted nor rejected and nothing is able to be brought back to HDFS. We have verified that the IP address that we are issuing the job from has been granted access to the database of interest.

Below is a snippet from the Sqoop output where the job is failing and the error that is with it.

18/08/03 07:58:38 INFO mapreduce.Job: Running job: job_1532959862591_1470
18/08/03 07:58:44 INFO mapreduce.Job: Job job_1532959862591_1470 running in uber mode : false
18/08/03 07:58:44 INFO mapreduce.Job: map 0% reduce 0%
18/08/03 08:00:56 INFO mapreduce.Job: Task Id : attempt_1532959862591_1470_m_000003_0, Status : FAILED
Error: java.lang.RuntimeException: java.lang.RuntimeException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

Do you have any suggestions or opinions as to why we are able to reach this point in the Sqoop job and then have it fail?



As a side note, we have another MySQL database version 5.5.60 that we are able to successfully Sqoop from using c/J 5.1.45 without any issues.




Thank you,
Cody