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

["Ayub Khan (JIRA)" <ji...@apache.org>]

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

Ayub Khan updated AMBARI-20505:
-------------------------------
    Summary: Changes needed to handle AMBARI-19623 in EU/RU scenario  (was: EU/RU changes to handle AMBARI-19623)

> 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
>             Fix For: trunk, 2.5.0
>
>
> 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)