Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of atm@cloudera.com designates
 209.85.216.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGB5D2bHtbSjE+uUrqDZD5h_ibG4vZwE0xd+Q3EAU3Gh18tcRQ@mail.gmail.com>
References: <3257865570275881418@unknownmsgid>
 <0C1D7754-D6EC-498F-9EAB-A7DC434FA28B@hortonworks.com>
 <52E6C33D.1040706@yahoo-inc.com>
 <22A900CF-64EC-4D7F-9EFF-F93A2086F487@hortonworks.com>
 <CACBYxKJ05=O+huK2jXse7OCYTH+u_Ud8uhH_rF1pBwJcOWXijQ@mail.gmail.com>
 <CACBYxKJ8vbZ28HgfKLWzENUKBZC-PTcOdjHQuqFX7ZgOVT5X9g@mail.gmail.com>
 <002397D9-6555-451C-AA48-916638C82638@hortonworks.com>
 <03000626-CF06-45D2-AEB4-1F9526F20E4E@hortonworks.com>
 <01E1D358-B8AF-4AB2-95C0-6120CA0C7970@hortonworks.com>
 <52E964E2.6090105@yahoo-inc.com>
 <CALEq1Z-Fk+1mrkBUEt7K3fqbXFfqT3nOucR75TXoA9Kf+B7ZfQ@mail.gmail.com>
 <CAGB5D2bHtbSjE+uUrqDZD5h_ibG4vZwE0xd+Q3EAU3Gh18tcRQ@mail.gmail.com>
From: "Aaron T. Myers" <atm@cloudera.com>
Date: Wed, 29 Jan 2014 18:52:52 -0500
Message-ID: 
 <CA+4052kcENv-Zk1F3TakmouKkhgeEs9iV2O_DLHr8wEe3Rf-NA@mail.gmail.com>
Subject: Re: Re-swizzle 2.3
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Cc: "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=001a1139b5d05fb41804f124a5df

--001a1139b5d05fb41804f124a5df
Content-Type: text/plain; charset=ISO-8859-1

I just filed this JIRA as a blocker for 2.3:
https://issues.apache.org/jira/browse/HADOOP-10310

The tl;dr is that JNs will not work with security enabled without this fix.
If others don't think that supporting QJM with security enabled warrants a
blocker for 2.3, then we can certainly lower the priority, but it seems
pretty important to me.

Best,
Aaron

--
Aaron T. Myers
Software Engineer, Cloudera


On Wed, Jan 29, 2014 at 6:24 PM, Andrew Wang <andrew.wang@cloudera.com>wrote:

> I just finished tuning up branch-2.3 and fixing up the HDFS and Common
> CHANGES.txt in trunk, branch-2, and branch-2.3. I had to merge back a few
> JIRAs committed between the swizzle and now where the fix version was 2.3
> but weren't in branch-2.3.
>
> I think the only two HDFS and Common JIRAs that are marked for 2.4 are
> these:
>
> HDFS-5842 Cannot create hftp filesystem when using a proxy user ugi and a
> doAs on a secure cluster
> HDFS-5781 Use an array to record the mapping between FSEditLogOpCode and
> the corresponding byte value
>
> Jing, these both look safe to me if you want to merge them back, or I can
> just do it.
>
> Thanks,
> Andrew
>
> On Wed, Jan 29, 2014 at 1:21 PM, Doug Cutting <cutting@apache.org> wrote:
> >
> > On Wed, Jan 29, 2014 at 12:30 PM, Jason Lowe <jlowe@yahoo-inc.com>
> wrote:
> > >  It is a bit concerning that the JIRA history showed that the target
> version
> > > was set at some point in the past but no record of it being cleared.
> >
> > Perhaps the version itself was renamed?
> >
> > Doug
>

--001a1139b5d05fb41804f124a5df--