[
https://issues.apache.org/jira/browse/ZOOKEEPER-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956391#comment-13956391
]
Hudson commented on ZOOKEEPER-1725:
-----------------------------------
SUCCESS: Integrated in ZooKeeper-trunk #2276 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2276/])
ZOOKEEPER-1725. Zookeeper Dynamic Conf writes out hostnames when IPs are
supplied (Alexander Shraer via michim) (michim:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1583495)
* /zookeeper/trunk/CHANGES.txt
*
/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java
*
/zookeeper/trunk/src/java/test/org/apache/zookeeper/server/quorum/QuorumServerTest.java
> 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: Michi Mutsuzaki
> 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)
