Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
trunk, 2.5.0
-
None
Description
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.
atlas.kafka.zookeeper.connection.timeout.ms=30000 atlas.kafka.zookeeper.session.timeout.ms=60000 atlas.audit.zookeeper.session.timeout.ms=60000