[jira] [Created] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

["Rakesh Kumar Singh (JIRA)" <ji...@apache.org>]

Rakesh Kumar Singh created ZOOKEEPER-2556:
---------------------------------------------

             Summary: peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
                 Key: ZOOKEEPER-2556
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556
             Project: ZooKeeper
          Issue Type: Bug
          Components: server
    Affects Versions: 3.5.1
            Reporter: Rakesh Kumar Singh
            Priority: Minor


peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

Steps to reproduce:-
1. Start zookeeper in cluster with one node as observer by configuring 
peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181
2. Start the cluster
3. start a client and change the node from observer to participant, the configuration related to peertype remained same though other things like clientport got from zoo.cfg

We should either remove this parameter or update with correct node type at run time



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)