[
https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331161#comment-15331161
]
Rakesh R commented on ZOOKEEPER-1045:
-------------------------------------
Few months back(Feb month) I have done one round of basic tests using old
patch. Installed 3 node cluster (all participants) uses 3.4.7 release. Say,
ZK1, ZK2, ZK3. Upgraded to 3.4.9-SNAPSHOT release starting from ZK1, ZK2, ZK3.
During each step of upgrade, verified the service availability using zkclients.
I haven't done rolling upgrade testing using the latest patch and
configurations. I will setup a kerb env and test it again. BTW [~hanm] has told
about testing, did you get a chance to experience it. Would be great to see
your feedback. Thanks!
To understand about the upgrade steps, please refer the steps mentioned in
{{QuorumAuthUpgradeTest.java}} unit test. While updating the cwiki page will
use this content and add rolling upgrade section in that.
> 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
> Fix For: 3.4.9, 3.5.3
>
> 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-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)
