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

2018-09-24 Thread Ted Yu (JIRA) 


 [ 
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
>Priority: Major
>
> 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
(v7.6.3#76005)

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

2018-08-19 Thread Ted Yu (JIRA) 


 [ 
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
>Priority: Major
>
> 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
(v7.6.3#76005)

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

2018-03-21 Thread Ted Yu (JIRA) 

 [ 
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
>Priority: Major
>
> 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
(v7.6.3#76005)

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

2018-03-01 Thread Ted Yu (JIRA) 

 [ 
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
>Priority: Major
>
> 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
(v7.6.3#76005)

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

2018-01-31 Thread Ted Yu (JIRA) 

 [ 
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
>Priority: Major
>
> 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
(v7.6.3#76005)

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

2017-12-26 Thread Ted Yu (JIRA) 

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

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

2017-12-08 Thread Ted Yu (JIRA) 

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

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

2017-10-25 Thread Ted Yu (JIRA) 

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

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

2017-10-09 Thread Ted Yu (JIRA) 

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

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

2017-09-21 Thread Ted Yu (JIRA) 

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

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

2017-09-09 Thread Ted Yu (JIRA) 

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

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

2017-08-24 Thread Ted Yu (JIRA) 

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

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

2017-07-26 Thread Ted Yu (JIRA) 

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

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

2017-06-27 Thread Ted Yu (JIRA) 

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

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

2017-06-01 Thread Ted Yu (JIRA) 

 [ 
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.3.15#6346)

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

2017-04-19 Thread Ted Yu (JIRA) 

 [ 
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.3.15#6346)

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

2017-03-26 Thread Ted Yu (JIRA) 

 [ 
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.3.15#6346)

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

2016-10-31 Thread Ted Yu (JIRA) 

 [ 
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.3.4#6332)

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

2016-10-25 Thread Ted Yu (JIRA) 

 [ 
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.3.4#6332)

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

2016-09-30 Thread Ted Yu (JIRA) 

 [ 
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.3.4#6332)

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

2016-09-18 Thread Ted Yu (JIRA) 

 [ 
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.3.4#6332)

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

2016-08-19 Thread Ted Yu (JIRA) 

 [ 
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.3.4#6332)

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

2016-06-20 Thread Ted Yu (JIRA) 

 [ 
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.3.4#6332)

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

2016-04-25 Thread Ted Yu (JIRA) 

 [ 
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.3.4#6332)

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

2016-03-28 Thread Ted Yu (JIRA) 

 [ 
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.3.4#6332)