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 2020/09/06 01:00: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=17191173#comment-17191173 ]
Ammar Khaku edited comment on CURATOR-526 at 9/6/20, 12:59 AM:
---------------------------------------------------------------
Did some digging this weekend - it appears that this is because 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]
If you don't set it this way, the config string returned by ZooKeeper doesn't have any client config, and so I believe Curator is doing the right thing by ignoring the config string.
Sadly in our case we run ZooKeeper via Exhibitor, so it's not very easy to set that string. I have a patch for Exhibitor [https://github.com/soabase/exhibitor/compare/master...akhaku:clientPort?expand=1] but it doesn't look like that project is very active. I can't open a PR because the project is marked as "Archived".
was (Author: akhaku):
Did some digging this weekend - it appears that this is because 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]
If you don't set it this way, the config string returned by ZooKeeper doesn't have any client config, and so I believe Curator is doing the right thing by ignoring the config string.
Sadly in our case we run ZooKeeper via Exhibitor, so it's not very easy to set that string. I have a patch for Exhibitor [https://github.com/soabase/exhibitor/compare/master...akhaku:clientPort?expand=1] but it doesn't look like that project is very active.
> 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)