You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Ammar Khaku (Jira)" <ji...@apache.org> on 2021/01/08 04:07:00 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17260978#comment-17260978 ]
Ammar Khaku edited comment on CURATOR-526 at 1/8/21, 4:06 AM:
--------------------------------------------------------------
That makes sense, yeah. Today there's an [explicit test|https://github.com/apache/curator/blob/apache-curator-4.3.0/curator-framework/src/test/java/org/apache/curator/framework/imps/TestReconfiguration.java#L372] to verify that the client connection string comes back empty for this case so perhaps the only required change is to replace that error with a debug message like the one [right below|https://github.com/apache/curator/blob/apache-curator-4.3.0/curator-framework/src/main/java/org/apache/curator/framework/imps/EnsembleTracker.java#L219].
was (Author: akhaku):
That makes sense, yeah. Today there's an [explicit test|https://github.com/apache/curator/blob/apache-curator-4.3.0/curator-framework/src/test/java/org/apache/curator/framework/imps/TestReconfiguration.java#L372] to verify that the client connection string comes back empty for this case so perhaps the only required change is to replace that error with a debug message like the one[ right below|https://github.com/apache/curator/blob/apache-curator-4.3.0/curator-framework/src/main/java/org/apache/curator/framework/imps/EnsembleTracker.java#L219].
> 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)