[
https://issues.apache.org/jira/browse/ZOOKEEPER-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980835#comment-13980835
]
Rakesh R commented on ZOOKEEPER-1695:
-------------------------------------
-119 is already used by NOTREADONLY. We have few set of KeeperException.Codes
defined without adding entry to CodeDeprecated interface.
{code}
/** Session moved to another server, so operation is ignored */
SESSIONMOVED (-118),
/** State-changing request is passed to read-only server */
NOTREADONLY (-119),
/** Attempts to remove a non-existing watcher */
NOWATCHER (-123);
{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, 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)
