[
https://issues.apache.org/jira/browse/AMBARI-19623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965438#comment-15965438
]
Hudson commented on AMBARI-19623:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7273 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7273/])
AMBARI-20505 ADDENDUM : Changes needed to handle AMBARI-19623 in EU/RU (mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=504e0b03d6d7c19f201379d0ae326a76c85e2bd1])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml
> Atlas startup failed with ZkTimeoutException exception, zookeeper timeout
> values are very low.
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-19623
> URL: https://issues.apache.org/jira/browse/AMBARI-19623
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk, 2.5.0
> Reporter: Ayub Pathan
> Assignee: Ayub Pathan
> Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19623.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}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
