zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2504) Enforce that server ids are unique in a cluster
Date Fri, 20 Jul 2018 18:58:00 GMT

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

Hadoop QA commented on ZOOKEEPER-2504:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12823503/ZOOKEEPER-2504.patch
  against trunk revision ed4689fbf81c56f09be26cf32ede66ad191f4aed.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3699//console

This message is automatically generated.

> Enforce that server ids are unique in a cluster
> -----------------------------------------------
>
>                 Key: ZOOKEEPER-2504
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2504
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Dan Benediktson
>            Assignee: Michael Han
>            Priority: Major
>         Attachments: ZOOKEEPER-2504.patch
>
>
> The leader will happily accept connections from learners that have the same server id
(i.e., due to misconfiguration). This can lead to various issues including non-unique session_ids
being generated by these servers.
> The leader can enforce that all learners come in with unique server IDs; if a learner
attempts to connect with an id that is already in use, it should be denied.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message