[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560559#comment-13560559
 ] 

Hudson commented on ZOOKEEPER-1625:
-----------------------------------

Integrated in ZooKeeper-trunk #1811 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/1811/])
    ZOOKEEPER-1625. zkServer.sh is looking for clientPort in config file, but 
it may
no longer be there with ZK-1411 (Alexander Shraer via michim) (Revision 1437257)

     Result = SUCCESS
michim : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1437257
Files : 
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/bin/zkServer.sh

                
> zkServer.sh is looking for clientPort in config file, but it may no longer be 
> there with ZK-1411
> ------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1625
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1625
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 3.5.0
>            Reporter: Alexander Shraer
>            Assignee: Alexander Shraer
>             Fix For: 3.5.0
>
>         Attachments: ZOOKEEPER-1625.patch
>
>
> zkServer.sh is currently looking for "clientPort" entry in the static 
> configuration file and uses it to contact the server. 
> With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
> appear in the separate dynamic configuration file. The "clientPort" entry may 
> no longer be in the static config file. 
> With the proposed patch zkServer.sh first looks in the old (static) config 
> file, then if clientPort is not there, it figures out the id of the server by 
> looking at myid file, and then using that id finds the client port in the 
> dynamic config file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to