[
https://issues.apache.org/jira/browse/AMBARI-14710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115165#comment-15115165
]
Hadoop QA commented on AMBARI-14710:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12784127/AMBARI-14710.3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5040//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5040//console
This message is automatically generated.
> Add retry logic for REST calls between Ambari and Ranger
> --------------------------------------------------------
>
> Key: AMBARI-14710
> URL: https://issues.apache.org/jira/browse/AMBARI-14710
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.2.0
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: trunk, 2.2.1
>
> Attachments: AMBARI-14710.1.patch, AMBARI-14710.2.patch,
> AMBARI-14710.3.patch, AMBARI-14710.trunk.patch
>
>
> Current implementation of {{check_ranger_login_urllib2}} in
> ranger_functions.py and ranger_functions_v2.py triggers the retry logic under
> the safe_retry decorator only for the Timeout error.
> This logic should be triggered for the exceptions also, to ensure that Ranger
> Admin is given enough time to start up before giving up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
