[
https://issues.apache.org/jira/browse/NIFI-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389564#comment-15389564
]
ASF GitHub Bot commented on NIFI-2253:
--------------------------------------
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/704#discussion_r71884405
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/cluster/ZooKeeperClientConfig.java
---
@@ -70,7 +75,10 @@ public static ZooKeeperClientConfig createConfig(final
Properties properties) {
if (connectString == null || connectString.trim().isEmpty()) {
throw new IllegalStateException("The '" +
NiFiProperties.ZOOKEEPER_CONNECT_STRING + "' property is not set in
nifi.properties");
}
-
+ final String cleanedConnectString =
cleanConnectString(connectString);
+ if (cleanedConnectString.isEmpty()) {
+ throw new IllegalStateException("The '" +
NiFiProperties.ZOOKEEPER_CONNECT_STRING + "' property is set but contains
unrecognized data in nifi.properties");
--- End diff --
This message could probably be made a little more clear - what is
"unrecognized data"? Perhaps spell out that the expected format is a
comma-separated list of <hostname>:<port> pairs.
> zookeeper server cannot interpret "space" in ZK connection string, in
> nifi.properties config file
> -------------------------------------------------------------------------------------------------
>
> Key: NIFI-2253
> URL: https://issues.apache.org/jira/browse/NIFI-2253
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Haimo Liu
> Assignee: Joseph Witt
> Priority: Minor
> Fix For: 1.0.0
>
>
> ZK server cannot interpret space in the following connection string
> (nifi.properties config file):
> nifi.zookeeper.connect.string=localhost:2181,localhost:2182,<space>localhost:2183
> in this case, multiple NIFI nodes will run in a standalone mode instead of
> operating in a clustered mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
