Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-1056

Implement connection resiliency in Sqoop using pluggable failure handlers



    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4.5
    • Component/s: connectors/sqlserver
    • Labels:


      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.


        1. SQOOP-1056-1057-combo.patch
          106 kB
          Venkat Ranganathan
        2. SQOOP-1056.3.patch
          73 kB
          Shuaishuai Nie
        3. SQOOP-1056.2.patch
          73 kB
          Shuaishuai Nie
        4. Sqoop Connection Resiliency.docx
          24 kB
          Shuaishuai Nie
        5. SQOOP-1056.1.patch
          74 kB
          Shuaishuai Nie

          Issue Links



              • Assignee:
                shuainie Shuaishuai Nie
                shuainie Shuaishuai Nie
              • Votes:
                0 Vote for this issue
                4 Start watching this issue


                • Created: