hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8315) Support SASL-authenticated ZooKeeper in ActiveStandbyElector
Date Fri, 27 Sep 2013 03:04:02 GMT

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

Todd Lipcon commented on HADOOP-8315:
-------------------------------------

[~phunt] suggested depending on ZK 3.4.5 but with the ZK 3.4.2 test jar. Unfortunately I tried
that, and the maven enforcer plugin wouldn't let me do it... and apparently the ZK folks are
having trouble getting 3.4.5 test jar published in the ASF repository.

I can get the 3.4.5 artifacts including the test jar published on either Cloudera's public
maven repository or in my Apache home directory. Does anyone have any preference? I'd like
to close this issue out.
                
> Support SASL-authenticated ZooKeeper in ActiveStandbyElector
> ------------------------------------------------------------
>
>                 Key: HADOOP-8315
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8315
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: auto-failover, ha
>    Affects Versions: Auto Failover (HDFS-3042)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-8315.txt, hadoop-8315_v2.txt
>
>
> Currently, if you try to use SASL-authenticated ZK with the ActiveStandbyElector, you
run into a couple issues:
> 1) We hit ZOOKEEPER-1437 - we need to wait until we see SaslAuthenticated before we can
make any requests
> 2) We currently throw a fatalError when we see the SaslAuthenticated callback on the
connection watcher
> We need to wait for ZK-1437 upstream, and then upgrade to the fixed version for #1. For
#2 we just need to add a case there and ignore it.

--
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

Mime
View raw message