[
https://issues.apache.org/jira/browse/ZOOKEEPER-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954452#comment-13954452
]
Hadoop QA commented on ZOOKEEPER-1725:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12637608/ZOOKEEPER-1725.patch
against trunk revision 1582943.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2000//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2000//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2000//console
This message is automatically generated.
> Zookeeper Dynamic Conf writes out hostnames when IPs are supplied
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-1725
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1725
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.0
> Reporter: Justin SB
> Assignee: Alexander Shraer
> Priority: Minor
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1725-ver1.patch, ZOOKEEPER-1725.patch,
> ZOOKEEPER-1725.patch
>
>
> When writing the dynamic configuration out, Zookeeper writes out hostnames,
> even if an IP address is supplied. These may not correctly round-trip (e.g.
> 127.0.0.1 might be written as localhost which may then resolve to 127.0.0.1
> and another IP address).
> This isn't actually causing problems for me right now, but seems very likely
> to cause hard-to-track-down problems in future.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
