Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <6017044.179141272159831702.JavaMail.jira@thor>
Date: Sat, 24 Apr 2010 21:43:51 -0400 (EDT)
From: "Jakob Homan (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-1054) Remove unnecessary sleep after failure
 in nextBlockOutputStream
In-Reply-To: <2126002829.391861269159087262.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Homan updated HDFS-1054:
------------------------------

    Status: Open  (was: Patch Available)

Canceling pending requested revision.

> Remove unnecessary sleep after failure in nextBlockOutputStream
> ---------------------------------------------------------------
>
>                 Key: HDFS-1054
>                 URL: https://issues.apache.org/jira/browse/HDFS-1054
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs client
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-1054.txt
>
>
> If DFSOutputStream fails to create a pipeline, it currently sleeps 6 seconds before retrying. I don't see a great reason to wait at all, much less 6 seconds (especially now that HDFS-630 ensures that a retry won't go back to the bad node). We should at least make it configurable, and perhaps something like backoff makes some sense.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.