ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20505) Changes needed to handle AMBARI-19623 in EU/RU scenario
Date Thu, 30 Mar 2017 21:25:41 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-20505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949870#comment-15949870
] 

Hadoop QA commented on AMBARI-20505:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12861237/AMBARI-20505_trunk_addendum.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 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/11246//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11246//console

This message is automatically generated.

> Changes needed to handle AMBARI-19623 in EU/RU scenario
> -------------------------------------------------------
>
>                 Key: AMBARI-20505
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20505
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk, 2.5.0
>            Reporter: Ayub Khan
>            Assignee: Vishal Suvagia
>            Priority: Blocker
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20505_branch-2.5.1.patch, AMBARI-20505_branch2.5.patch, AMBARI-20505.patch,
AMBARI-20505_trunk_addendum.patch, AMBARI-20505_trunk.patch
>
>
> Currently zookeeper connect/session timeout values for atlas are set to 200/400 ms respectively
which are very low and not practical/recommended values. Due to this atlas startup fails more
frequently.
> The jira is set recommended values for zookeeper timeout configuration.
> {noformat}
> atlas.kafka.zookeeper.connection.timeout.ms=30000
> atlas.kafka.zookeeper.session.timeout.ms=60000
> atlas.audit.zookeeper.session.timeout.ms=60000
> {noformat} 
> As per the comment by [~afernandez] in the below link, these changes has to be handled
in EU/RU scenario.
> https://issues.apache.org/jira/browse/AMBARI-19623?focusedCommentId=15830880&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15830880



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message