You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Cam McKenzie (Jira)" <ji...@apache.org> on 2021/07/19 22:01:01 UTC
[jira] [Updated] (CURATOR-526) Error logged for valid config -
"Invalid config event received: {properties}"
[ https://issues.apache.org/jira/browse/CURATOR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cam McKenzie updated CURATOR-526:
---------------------------------
Fix Version/s: (was: 5.1.1)
5.2.0
> 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.2.0
>
> Time Spent: 1.5h
> 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)