You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Keith Turner (Created) (JIRA)" <ji...@apache.org> on 2012/02/15 23:47:59 UTC

[jira] [Created] (ACCUMULO-408) Large bulk imports timing out

Large bulk imports timing out
-----------------------------

                 Key: ACCUMULO-408
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-408
             Project: Accumulo
          Issue Type: Bug
            Reporter: Keith Turner
            Priority: Critical
             Fix For: 1.4.0


Large bulk imports that take more than 2 minutes to process are failing.  The master ask a tablet sever to bulk import the files and times out after 2 minutes.  It retries, but the retry will take over 2 minutes.  Eventually it gives up and starts coping all of the data to the fail dir which takes forever.  This copy is all through the master and for large data basically never completes.  The bulk import threads on the tablet server probably complete eventually, so the data is still there.

The master should not time these request out.

--
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

        

[jira] [Updated] (ACCUMULO-408) Large bulk imports timing out

Posted by "Keith Turner (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Turner updated ACCUMULO-408:
----------------------------------

    Component/s: tserver
                 master
    
> Large bulk imports timing out
> -----------------------------
>
>                 Key: ACCUMULO-408
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-408
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>            Reporter: Keith Turner
>            Priority: Critical
>             Fix For: 1.4.0
>
>
> Large bulk imports that take more than 2 minutes to process are failing.  The master ask a tablet sever to bulk import the files and times out after 2 minutes.  It retries, but the retry will take over 2 minutes.  Eventually it gives up and starts coping all of the data to the fail dir which takes forever.  This copy is all through the master and for large data basically never completes.  The bulk import threads on the tablet server probably complete eventually, so the data is still there.
> The master should not time these request out.

--
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

        

[jira] [Updated] (ACCUMULO-408) Large bulk imports timing out

Posted by "Keith Turner (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Turner updated ACCUMULO-408:
----------------------------------

    Fix Version/s:     (was: 1.4.0)
                   1.5.0

A fix for this was checked in svn commit #1245631.  This fix is still susceptible to the timeout issue.  This fix makes the problem much less likely and is the fix for 1.4.x.  For 1.5, we may want to consider a fix that is not susceptible to the timeout issue.
                
> Large bulk imports timing out
> -----------------------------
>
>                 Key: ACCUMULO-408
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-408
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>            Reporter: Keith Turner
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> Large bulk imports that take more than 2 minutes to process are failing.  The master ask a tablet sever to bulk import the files and times out after 2 minutes.  It retries, but the retry will take over 2 minutes.  Eventually it gives up and starts coping all of the data to the fail dir which takes forever.  This copy is all through the master and for large data basically never completes.  The bulk import threads on the tablet server probably complete eventually, so the data is still there.
> The master should not time these request out.

--
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

        

[jira] [Updated] (ACCUMULO-408) Large bulk imports timing out

Posted by "Keith Turner (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Turner updated ACCUMULO-408:
----------------------------------

    Affects Version/s: 1.4.0
    
> Large bulk imports timing out
> -----------------------------
>
>                 Key: ACCUMULO-408
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-408
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> Large bulk imports that take more than 2 minutes to process are failing.  The master ask a tablet sever to bulk import the files and times out after 2 minutes.  It retries, but the retry will take over 2 minutes.  Eventually it gives up and starts coping all of the data to the fail dir which takes forever.  This copy is all through the master and for large data basically never completes.  The bulk import threads on the tablet server probably complete eventually, so the data is still there.
> The master should not time these request out.

--
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