You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2014/04/25 08:14:18 UTC

[jira] [Commented] (ZOOKEEPER-1695) Inconsistent error code and type for new errors introduced by dynamic reconfiguration

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980732#comment-13980732 ] 

Rakesh R commented on ZOOKEEPER-1695:
-------------------------------------

Hi [~michim],
Can we move up the following err sequence numbers, as we are moving 'ZNEWCONFIGNOQUORUM = -120  and ZRECONFIGINPROGRESS = -121' to system errors ?
{code}
  ZEPHEMERALONLOCALSESSION = -122, /*!< Attempt to create ephemeral node on a local session */
  ZNOWATCHER = -123 /*!< The watcher couldn't be found */
{code}

> Inconsistent error code and type for new errors introduced by dynamic reconfiguration  
> ---------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1695
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1695
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.5.0
>            Reporter: Thawan Kooburat
>            Assignee: Michi Mutsuzaki
>            Priority: Blocker
>             Fix For: 3.5.0
>
>         Attachments: ZOOKEEPER-1695.patch
>
>
> From KeeperException.Code, RECONFIGINPROGRESS and NEWCONFIGNOQUORUM are declared as system errors. However, their error code suggested that they are API errors. 
> We either need to move it to the right type or use the code from the right range



--
This message was sent by Atlassian JIRA
(v6.2#6252)