You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Rajesh Singh (JIRA)" <ji...@apache.org> on 2019/06/03 23:24:00 UTC

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

Rajesh Singh created CURATOR-526:
------------------------------------

             Summary: 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
             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
(v7.6.3#76005)