[
https://issues.apache.org/jira/browse/AMBARI-20505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937438#comment-15937438
]
Alejandro Fernandez edited comment on AMBARI-20505 at 3/23/17 12:19 AM:
------------------------------------------------------------------------
Pushed to trunk, commit ca2c83582e135bb5410b62775292a780e68757eb
STILL NEED TO COMMIT TO branch-2.5 after the RC candidate is done and the 2.5
release is done. Leave the Jira open until then.
was (Author: afernandez):
Pushed to trunk, commit ca2c83582e135bb5410b62775292a780e68757eb
STILL NEED TO COMMIT TO branch-2.5 after the RC candidate is done and the 2.5
release is done.
> 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.0
>
> Attachments: AMBARI-20505_branch2.5.patch, AMBARI-20505.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)
