Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Wed, 4 Jul 2012 21:55:14 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <910302978.6330.1341438914476.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <512483384.3725.1337973383303.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (AMBARI-422) Increase Threshold For Number Of
 Successive Backend Connection Failures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli updated AMBARI-422:
-------------------------------------------

    Affects Version/s:     (was: ambari-186)
                       0.9.0
    
> Increase Threshold For Number Of Successive Backend Connection Failures
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-422
>                 URL: https://issues.apache.org/jira/browse/AMBARI-422
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: Varun Kapoor
>            Assignee: Varun Kapoor
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-422.patch
>
>
> Bad network connectivity makes the current limit of 5 HTTP connection errors too low - I'm bumping this up to 25 to be more tolerant, since each connection is attempted after 3 seconds, so 2 tries buys us 75 seconds.

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