Github user Vile2539 commented on a diff in the pull request:
https://github.com/apache/curator/pull/205#discussion_r127615377
--- Diff:
curator-framework/src/test/java/org/apache/curator/framework/imps/TestReconfiguration.java
---
@@ -313,6 +313,38 @@ public void testNewMembers() throws Exception
}
}
+ @Test
+ public void testConfigToConnectionStringNormal() throws Exception
+ {
+ String config =
"server.1=10.1.2.3:2888:3888:participant;10.2.3.4:2181";
+ String configString =
EnsembleTracker.configToConnectionString(toQuorumVerifier(config.getBytes()));
+ Assert.assertEquals("10.2.3.4:2181", configString);
+ }
+
+ @Test
+ public void testConfigToConnectionStringNoClientAddr() throws Exception
+ {
+ String config = "server.1=10.1.2.3:2888:3888:participant;2181";
+ String configString =
EnsembleTracker.configToConnectionString(toQuorumVerifier(config.getBytes()));
+ Assert.assertEquals("10.1.2.3:2181", configString);
+ }
+
+ @Test
+ public void testConfigToConnectionStringWildcardClientAddr() throws
Exception
+ {
+ String config =
"server.1=10.1.2.3:2888:3888:participant;0.0.0.0:2181";
--- End diff --
It doesn't look like Zookeeper supports IPv6 addresses in 3.5.1-alpha
(which is what Curator seems to be using). This appears to be fixed in
Zookeeper 3.5.2 and 3.6.0:
https://issues.apache.org/jira/browse/ZOOKEEPER-1460
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
