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

Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2008/11/05 20:05:44 UTC

[jira] Updated: (ZOOKEEPER-217) Errors in config file

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

Patrick Hunt updated ZOOKEEPER-217:
-----------------------------------

        Fix Version/s:     (was: 3.0.0)
                       3.1.0
                       3.0.1
    Affects Version/s:     (was: 3.0.1)
                       3.0.0

> Errors in config file
> ---------------------
>
>                 Key: ZOOKEEPER-217
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-217
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.0.0
>            Reporter: Flavio Paiva Junqueira
>            Priority: Minor
>             Fix For: 3.0.1, 3.1.0
>
>
> Discussing 209 with Ben today, we thought that it would be better to have the parse method of QuorumPeerConfig returning a boolean that indicates whether the configuration is good or not, and let the caller decide whether to exit or not. Currently we execute a System.exit() on QuorumPeerConfig.parse when we have a critical configuration error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.