You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2013/04/05 23:49:22 UTC

[jira] [Updated] (HADOOP-8315) Support SASL-authenticated ZooKeeper in ActiveStandbyElector

     [ https://issues.apache.org/jira/browse/HADOOP-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HADOOP-8315:
--------------------------------

    Attachment: hadoop-8315.txt

Attached patch upgrades to ZK 3.4.5 (which includes ZOOKEEPER-1437) and adds a case to the ZK callback to avoid a FATAL error on SaslAuthenticated.

I read through the notes on ZK-1437 but didn't follow every last bit. Pat -- from your perspective, the above two steps should be sufficient, right? ie we don't need to actually wait on SaslAuthenticated before performing other actions, since the patch makes the other actions automatically delay until auth is complete?
                
> 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
>         Attachments: hadoop-8315.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