[jira] [Commented] (CURATOR-526) Error logged for valid config - "Invalid config event received: {properties}"

["Mate Szalay-Beko (Jira)" <ji...@apache.org>]

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

Mate Szalay-Beko commented on CURATOR-526:
------------------------------------------

{quote}as of ZooKeeper 3.5.0, clientPort should be specified via the server statements and not via a separate config property [https://zookeeper.apache.org/doc/r3.5.3-beta/zookeeperReconfig.html#ch_reconfig_format]
{quote}
I'm not sure if this is true. The ZooKeeper docs are not really clear here. Even in ZooKeeper 3.6.2, in the same document ([https://zookeeper.apache.org/doc/r3.6.2/zookeeperReconfig.html]) states in the section *_Backward compatibility:_*
{quote}Backward compatibility
 We still support the old configuration format. For example, the following configuration file is acceptable (but not recommended):

zoo_replicated1.cfg
 tickTime=2000
 dataDir=/zookeeper/data/zookeeper1
 initLimit=5
 syncLimit=2
 clientPort=2791
 server.1=125.23.63.23:2780:2783:participant
 server.2=125.23.63.24:2781:2784:participant
 server.3=125.23.63.25:2782:2785:participant
{quote}
Also when you are using both secure (SSL) and unsecure (non-SSL) ports in ZooKeeper, then it is unclear for me what to put to the end of the "server" string.

I think this is still a bug and the server config should be parsed by Curator even without the client config.

What do you think?

> Error logged for valid config - "Invalid config event received: {properties}"
> -----------------------------------------------------------------------------
>
>                 Key: CURATOR-526
>                 URL: https://issues.apache.org/jira/browse/CURATOR-526
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 4.0.1
>            Reporter: Rajesh Singh
>            Priority: Major
>             Fix For: awaiting-response
>
>
> Curator Framework v4.0.1 - EnsembleTracker.processConfigData(byte[] data) (Ln: 157)- seems to be logging error for valid configs when the config string obtained from Zookeeper does not have the client info in it. 
> As per the docs the config string should conform to below formats:
> *server_config* or *server_config*;*client_config* where server_config is host:port:port or host:port:port:type and client_config is port or host:port
> In our case it conforms to the first pattern i.e. *server_config* with host:port:port:type



--
This message was sent by Atlassian Jira
(v8.3.4#803005)