You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Kazuaki Banzai (JIRA)" <ji...@apache.org> on 2016/03/16 13:45:33 UTC
[jira] [Updated] (ZOOKEEPER-2391) setMin/MaxSessionTimeout of
ZookeeperServer are implemented in quite a weak way
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kazuaki Banzai updated ZOOKEEPER-2391:
--------------------------------------
Attachment: ZOOKEEPER-2391.patch
There are two possible ways to respond to invalid parameters: Call using invalid parameters could be ignored, or the method could throw an exception. The second approach finds flawed code more proactively but may cause problems with existing faulty clients. The patch implements the second solution, because it would be better in the long term to adapt strict parameter checking.
> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak way
> -------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2391
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2391
> Project: ZooKeeper
> Issue Type: Bug
> Components: documentation, server
> Reporter: Kazuaki Banzai
> Priority: Minor
> Attachments: ZOOKEEPER-2391.patch
>
>
> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak way.
> * -1 restores the default, but this is not documented.
> * values < -1 are permitted but make no sense.
> * min > max is permitted but makes not sense.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)