[
https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306209#comment-15306209
]
Rakesh R commented on ZOOKEEPER-1045:
-------------------------------------
[~hanm], I could see a chance of the following sock connection refused
exception while connecting to {{election port}}. I think this is because the
{{Listener}} is binding the election server port in a separate thread. I've
tried an attempt by adding grace period in the tests before connecting to this
port. Could you please verify it again using the latest patch.
{code}
2016-05-29 10:43:57,029 [myid:] - WARN [Thread-1:QuorumCnxManager@502] -
Cannot open channel to 1 at election address /0.0.0.0:11235
java.net.ConnectException: Connection refused
{code}
> Quorum Peer mutual authentication
> ---------------------------------
>
> Key: ZOOKEEPER-1045
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Reporter: Eugene Koontz
> Assignee: Rakesh R
> Priority: Critical
> Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch,
> 1045_failing_phunt.tar.gz, ZK-1045-test-case-failure-logs.zip,
> ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf,
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch,
> ZOOKEEPER-1045-br-3-4.patch
>
>
> ZOOKEEPER-938 addresses mutual authentication between clients and servers.
> This bug, on the other hand, is for authentication among quorum peers.
> Hopefully much of the work done on SASL integration with Zookeeper for
> ZOOKEEPER-938 can be used as a foundation for this enhancement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
