Re: [VOTE] Plan to create release candidate Monday 3/18
+1. On Mon, Mar 11, 2013 at 11:52 AM, Colin McCabe wrote: > +1 (non-binding) > > best, > Colin > > > On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley wrote: > > > Hi all, > > I have created branch-1.2 from branch-1, and propose to cut the first > > release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as > > soon thereafter as I can achieve a stable build. > > > > Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft > release > > notes are available at .../branch-1.2/src/docs/releasenotes.html in the > > sources. > > > > Any non-destabilizing patches committed to branch-1.2 during the coming > > week (and of course also committed to branch-1) will be included in the > RC. > > However, at this point I request that any big new developments not yet > in > > branch-1.2 be targeted for 1.3. > > > > Release plans have to be voted on too, so please vote '+1' to approve > this > > plan. Voting will close on Sunday 3/17 at 8:30pm PDT. > > > > Thanks, > > --Matt > > (release manager) > > >
[jira] [Resolved] (HADOOP-9395) jetty7 and hadoop 1.1.x
[ https://issues.apache.org/jira/browse/HADOOP-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Lu resolved HADOOP-9395. - Resolution: Duplicate Fix Version/s: (was: 1.1.3) (was: 1.2.0) Thanks for the patch Alexey! The usual process here is to patch trunk first then backport to branch-1. I'll assign HADOOP-8515 to you. Let me know if you don't want to work on it :) > jetty7 and hadoop 1.1.x > --- > > Key: HADOOP-9395 > URL: https://issues.apache.org/jira/browse/HADOOP-9395 > Project: Hadoop Common > Issue Type: Improvement > Components: build, net >Affects Versions: 1.1.2 > Environment: FreeBSD 9.1+ZFS.2 xeon 5640,12Gb regDDR3,4 HDD 2Tb. >Reporter: Alexey Babutin >Priority: Minor > Labels: patch > Attachments: hadoop_jetty.patch > > > Change jetty6 to jetty7 -- 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
[jira] [Created] (HADOOP-9395) jetty7 and hadoop 1.1.x
Alexey Babutin created HADOOP-9395: -- Summary: jetty7 and hadoop 1.1.x Key: HADOOP-9395 URL: https://issues.apache.org/jira/browse/HADOOP-9395 Project: Hadoop Common Issue Type: Improvement Components: build, net Affects Versions: 1.1.2 Environment: FreeBSD 9.1+ZFS.2 xeon 5640,12Gb regDDR3,4 HDD 2Tb. Reporter: Alexey Babutin Priority: Minor Fix For: 1.2.0, 1.1.3 Change jetty6 to jetty7 -- 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
[jira] [Created] (HADOOP-9394) Port findHangingTest.sh from HBase to Hadoop
Andrew Wang created HADOOP-9394:
---
Summary: Port findHangingTest.sh from HBase to Hadoop
Key: HADOOP-9394
URL: https://issues.apache.org/jira/browse/HADOOP-9394
Project: Hadoop Common
Issue Type: Improvement
Reporter: Andrew Wang
Assignee: Andrew Wang
Priority: Minor
HBase has this handy {{dev-support/findHangingTests.sh}} script, which parses
Jenkins consoleText and finds hanging tests for you. This has been especially
useful for identifying balancer test timeouts (see HDFS-4376 and HDFS-4261).
It'd be nice to have this in our own {{dev-support}} directory.
--
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
[jira] [Created] (HADOOP-9393) TestRPC fails with JDK7
Andrew Wang created HADOOP-9393:
---
Summary: TestRPC fails with JDK7
Key: HADOOP-9393
URL: https://issues.apache.org/jira/browse/HADOOP-9393
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Andrew Wang
Assignee: Andrew Wang
Since the test order is different with JDK7, we hit an error in
{{TestRPC#testStopsAllThreads}} on the initial assertEquals. This is because
{{testRPCInterruptedSimple}} and {{testRPCInterrupted}} don't stop the server
after they finish, leaving some threads around.
--
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
Re: [VOTE] Plan to create release candidate Monday 3/18
+1 (non-binding) best, Colin On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley wrote: > Hi all, > I have created branch-1.2 from branch-1, and propose to cut the first > release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as > soon thereafter as I can achieve a stable build. > > Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release > notes are available at .../branch-1.2/src/docs/releasenotes.html in the > sources. > > Any non-destabilizing patches committed to branch-1.2 during the coming > week (and of course also committed to branch-1) will be included in the RC. > However, at this point I request that any big new developments not yet in > branch-1.2 be targeted for 1.3. > > Release plans have to be voted on too, so please vote '+1' to approve this > plan. Voting will close on Sunday 3/17 at 8:30pm PDT. > > Thanks, > --Matt > (release manager) >
Re: [VOTE] Plan to create release candidate Monday 3/18
On 11 March 2013 03:38, Matt Foley wrote: > Hi all, > I have created branch-1.2 from branch-1, and propose to cut the first > release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as > soon thereafter as I can achieve a stable build. > > Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release > notes are available at .../branch-1.2/src/docs/releasenotes.html in the > sources. > > Any non-destabilizing patches committed to branch-1.2 during the coming > week (and of course also committed to branch-1) will be included in the RC. > However, at this point I request that any big new developments not yet in > branch-1.2 be targeted for 1.3. > > Release plans have to be voted on too, so please vote '+1' to approve this > plan. Voting will close on Sunday 3/17 at 8:30pm PDT. > +1
Re: [VOTE] Plan to create release candidate Monday 3/18
+1 (non-binding) On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley wrote: > Hi all, > I have created branch-1.2 from branch-1, and propose to cut the first > release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as > soon thereafter as I can achieve a stable build. > > Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release > notes are available at .../branch-1.2/src/docs/releasenotes.html in the > sources. > > Any non-destabilizing patches committed to branch-1.2 during the coming > week (and of course also committed to branch-1) will be included in the RC. > However, at this point I request that any big new developments not yet in > branch-1.2 be targeted for 1.3. > > Release plans have to be voted on too, so please vote '+1' to approve this > plan. Voting will close on Sunday 3/17 at 8:30pm PDT. > > Thanks, > --Matt > (release manager) >
Re: [PROPOSAL] Hadoop branch-1.2
On 10 March 2013 18:32, Suresh Srinivas wrote: > Steve, is there a timeline all these changes will be ready? If it is not > going to be > ready soon, perhaps these changes could be consider for 1.3? > > Suresh, I've put everything into https://issues.apache.org/jira/browse/HADOOP-9258 - the tests and the patches for S3 and S3N. Data loss is only going to happen if you go rename(srcDir, srcDir) or rename(srcDir,srcDir/child); nobody has ever reported it. We have to decide whether this is critical enough to get in, or postpone to 1.3. Given this is a last minute change and the changes to the S3FileSystem's rename() operation are significant, delaying to 1.3 may actually be safer. your choice -steve
RE: Contribution to "Project Rhino"
Hi Thomas, My name is Kai from project Rhino team now working on the topic of "Token based authentication and single sign on". I am glad to know that you are interested in this topic and I'd love to work with you for that. > Hello Devs, > My name is Thomas and I'm currently doing my master research on "Secure > Hadoop cluster over inter-cloud environment'. I've found that some of you > are working on Hadoop security though the "Project Rhino", that's why I'd > like to contribute to this project. > To be honest, i'm a bit afraid because I have only a fixed amount of time ( > ~4 months for development) to produce something and have no experience with > the open source Hadoop. Moreover, i'm working alone. That's the fun part about the Apache community, you can almost always find someone else to work with you. You and I can get this going and I am sure others with interest on this area will join in to help. > I'd like to know your opinion about what should be feasible for me. I created a Jira entry here: https://issues.apache.org/jira/browse/HADOOP-9392, let's continue our discussion there. > Actually, I'm kinda interested by the third point "Token based authentication > and single sign on" because nobody has started it yet and it is something > that could be interesting for my "intercloud environment". > Plus, if you have some ideas, hints, documentations or links to mailling list > discussion that could help me for the start, it would be wonderful ^^. Please see the jira for our initial goals, we can continue the discussion from there. > Thanks. > Best regards. > N. Thomas
[jira] [Created] (HADOOP-9392) Token based authentication and Single Sign On
Kai Zheng created HADOOP-9392: - Summary: Token based authentication and Single Sign On Key: HADOOP-9392 URL: https://issues.apache.org/jira/browse/HADOOP-9392 Project: Hadoop Common Issue Type: New Feature Components: security Reporter: Kai Zheng Fix For: 3.0.0 This is an umbrella entry for one of project Rhino’s topic, for details of project Rhino, please refer to https://github.com/intel-hadoop/project-rhino/. The major goal for this entry as described in project Rhino was “Core, HDFS, ZooKeeper, and HBase currently support Kerberos authentication at the RPC layer, via SASL. However this does not provide valuable attributes such as group membership, classification level, organizational identity, or support for user defined attributes. Hadoop components must interrogate external resources for discovering these attributes and at scale this is problematic. There is also no consistent delegation model. HDFS has a simple delegation capability, and only Oozie can take limited advantage of it. We will implement a common token based authentication framework to decouple internal user and service authentication from external mechanisms used to support it (like Kerberos)” We’d like to start our work from Hadoop-Common and try to provide common facilities by extending existing authentication framework which support: 1. Pluggable token provider interface 2. Pluggable token verification protocol and interface 3. Security mechanism to distribute secrets in cluster nodes 4. Delegation model of user authentication -- 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
