Shuaishuai Nie created SQOOP-1056:
-------------------------------------
Summary: Implement connection resiliency in Sqoop using pluggable
failure handlers
Key: SQOOP-1056
URL: https://issues.apache.org/jira/browse/SQOOP-1056
Project: Sqoop
Issue Type: Improvement
Components: connectors/sqlserver
Reporter: Shuaishuai Nie
Implement a pluggable way for handling connection failures, and/or intermittent
errors in Sqoop. This is especially crucial in environments where the
probability of connections getting reset or throttled is high.
In case of intermittent failures in Sqoop, due to connection losses or server
throttling, Sqoop does not recover from those failures. As a result, the
running Sqoop task would eventually fail, and a new task is started. In those
cases, Sqoop does not always guarantee that tasks can safely be restarted. For
example, if part of the records is already committed to the database, then
restarting the task would result in some failures like primary key violations.
Even for Sqoop jobs which commit the records only at the end of the task, any
failures towards the end of the task would involve reprocessing the whole range
of split owned by the task, and any progress is lost.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
