[jira] [Commented] (AMBARI-20505) Changes needed to handle AMBARI-19623 in EU/RU scenario

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

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/12859746/AMBARI-20505.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 ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/11112//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11112//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
>             Fix For: trunk
>
>         Attachments: AMBARI-20505.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)