[
https://issues.apache.org/jira/browse/CURATOR-526?focusedWorklogId=569872&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-569872
]
ASF GitHub Bot logged work on CURATOR-526:
------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Mar/21 17:17
Start Date: 22/Mar/21 17:17
Worklog Time Spent: 10m
Work Description: akhaku commented on a change in pull request #382:
URL: https://github.com/apache/curator/pull/382#discussion_r598921590
##########
File path:
curator-framework/src/main/java/org/apache/curator/framework/imps/EnsembleTracker.java
##########
@@ -211,7 +211,7 @@ private void processConfigData(byte[] data) throws Exception
}
else
{
- log.error("Invalid config event received: {}", properties);
+ log.debug("Invalid config event received: {}", properties);
Review comment:
It is indeed the noise. I picked `debug` over `info` because the log
message at 219 below is for a similar case (missing config) and is at `debug`,
but happy to change it to `info` instead, thoughts?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 569872)
Time Spent: 40m (was: 0.5h)
> 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
>
> Time Spent: 40m
> 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)
