You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/04/12 06:07:41 UTC

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

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

Hudson commented on AMBARI-20505:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1387 (See [https://builds.apache.org/job/Ambari-branch-2.5/1387/])
AMBARI-20505 : Changes needed to handle AMBARI-19623 in EU/RU scenario (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1b75e371dcbe4ec739a55318d9cee06ca90b917a])
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml


> 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 Pathan
>            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)