You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Mark Harwood (JIRA)" <ji...@apache.org> on 2008/08/29 17:00:44 UTC
[jira] Updated: (ZOOKEEPER-127) Use of non-standard election ports
in config breaks services
[ https://issues.apache.org/jira/browse/ZOOKEEPER-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Harwood updated ZOOKEEPER-127:
-----------------------------------
Attachment: mhPortChanges.patch
This is a snapshot of the changes I had been thinking of making.
Note: this DOES NOT COMPILE!
If you apply the patch you can see the compile error at the point in RecvWorker where this ran out of steam.
It seems that in order to know which QourumPeer was talking to another you would need to pass "myid" as part of the comms protocol - there would be no other way of server A knowing if server B or server C had connected to it if we allow >1 Quorum peer per machine - the source IP address obtained from SocketChannel.socket().getInetAddress() is not sufficient to distinguish between them.
That seems like a much bigger change that I don't feel particularly well equipped to take on just yet.
> Use of non-standard election ports in config breaks services
> ------------------------------------------------------------
>
> Key: ZOOKEEPER-127
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-127
> Project: Zookeeper
> Issue Type: Bug
> Components: quorum
> Affects Versions: 3.0.0
> Reporter: Mark Harwood
> Priority: Minor
> Attachments: mhPortChanges.patch
>
>
> In QuorumCnxManager.toSend there is a call to create a connection as follows:
> channel = SocketChannel.open(new InetSocketAddress(addr, port));
> Unfortunately "addr" is the ip address of a remote server while "port" is the electionPort of *this* server.
> As an example, given this configuration (taken from my zoo.cfg)
> server.1=10.20.9.254:2881
> server.2=10.20.9.9:2882
> server.3=10.20.9.254:2883
> Server 3 was observed trying to make a connection to host 10.20.9.9 on port 2883 and obviously failing.
> In tests where all machines use the same electionPort this bug would not manifest itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.