You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/10/10 05:00:11 UTC

[jira] [Updated] (AMBARI-14163) zookeeper session timeout for hbase should take zookeeper tickTime into account

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

Ted Yu updated AMBARI-14163:
----------------------------
    Description: 
With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds.
The change was accepted.

However, such timeout is not reachable (it is > 20 times tickTime).
Ambari should detect such scenario and warn user.

  was:
With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds.
The change was accepted.

However, such timeout is not reachable (it is > 20 times tickTime).

Ambari should detect such scenario and warn user.


> zookeeper session timeout for hbase should take zookeeper tickTime into account
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-14163
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14163
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Ted Yu
>
> With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds.
> The change was accepted.
> However, such timeout is not reachable (it is > 20 times tickTime).
> Ambari should detect such scenario and warn user.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)