[
https://issues.apache.org/jira/browse/CURATOR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli resolved CURATOR-526.
-------------------------------------
Fix Version/s: (was: awaiting-response)
5.1.1
Resolution: Fixed
Issue resolved by pull request 382
[https://github.com/apache/curator/pull/382]
> 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
> Assignee: Enrico Olivelli
> Priority: Major
> Fix For: 5.1.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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)
