You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Arvind Prabhakar (Commented) (JIRA)" <ji...@apache.org> on 2011/12/28 06:09:30 UTC
[jira] [Commented] (SQOOP-418) MySQLAuthTest hangs when run against
MySQL 5.5.3 or higher version
[ https://issues.apache.org/jira/browse/SQOOP-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176448#comment-13176448 ]
Arvind Prabhakar commented on SQOOP-418:
----------------------------------------
This is because in recent version of MySQL 5.5.x the concept of metadata locking was introduced which causes DDL operations to timeout if the table in question has an unclosed transaction that ran a DML operation.
The implementation of DBRecordReader in Sqoop is such that if a failure occurs, it will raise the exception without closing the associated statement/connection it was working with. This condition is triggered by the MySQLAuthTest which then hangs until timeout.
> MySQLAuthTest hangs when run against MySQL 5.5.3 or higher version
> ------------------------------------------------------------------
>
> Key: SQOOP-418
> URL: https://issues.apache.org/jira/browse/SQOOP-418
> Project: Sqoop
> Issue Type: Bug
> Reporter: Arvind Prabhakar
> Assignee: Arvind Prabhakar
>
> When running MySQLAuthTest against MySQL version 5.5.3 or higher, the test will hang and eventually fail due to timeout.
--
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