ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19623) Atlas startup failed with ZkTimeoutException exception, zookeeper timeout values are very low.
Date Fri, 20 Jan 2017 00:26:26 GMT

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

Alejandro Fernandez updated AMBARI-19623:
-----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Pushed to trunk, commit bbacefd44a52bfd0a82c6067f9974944623cfdec
branch-2.5, commit 9142e2d6c06ad50dfa01dc4d2f1ef06b834141d9

> 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 Khan
>            Assignee: Ayub Khan
>            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.4#6332)

Mime
View raw message