I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.

Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.

thanks,
Arun

On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:

> Folks,
>
>  I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>
>  # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>  # Pending security work for YARN (anything for HDFS w.r.t HA?)
>  # RM Restart (MAPREDUCE-4326)
>  # Container re-use (MAPREDUCE-3902)
>  # Multi-resource scheduling for CS (MAPREDUCE-4327).
>
>  If you would like others please set the 'Target Version' and I'll watch that list.
>
> thanks,
> Arun
>
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha RC?

On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
> I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.
>
> Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.
>
> thanks,
> Arun
>
> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>
>> Folks,
>>
>>  I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>>
>>  # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>>  # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>  # RM Restart (MAPREDUCE-4326)
>>  # Container re-use (MAPREDUCE-3902)
>>  # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>
>>  If you would like others please set the 'Target Version' and I'll watch that list.
>>
>> thanks,
>> Arun
>>
>>
>> --
>> Arun C. Murthy
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>>
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>

I'll try and shoot for end of month, but will depend on performance work and how much we'll need to get to parity with hadoop-1.x on branch-2 etc., even though hadoop-0.23 was there. Fingers crossed.

thanks,
Arun

On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:

> Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha RC?
>
> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>> I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.
>>
>> Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.
>>
>> thanks,
>> Arun
>>
>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>>
>>> Folks,
>>>
>>> I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>>>
>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>> # RM Restart (MAPREDUCE-4326)
>>> # Container re-use (MAPREDUCE-3902)
>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>>
>>> If you would like others please set the 'Target Version' and I'll watch that list.
>>>
>>> thanks,
>>> Arun
>>>
>>>
>>> --
>>> Arun C. Murthy
>>> Hortonworks Inc.
>>> http://hortonworks.com/
>>>
>>>
>>
>> --
>> Arun C. Murthy
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>>

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Hey Arun,

Are you still planning on releasing this branch?  It's been a couple
of months and branch-2.1.0-alpha wasn't compiling for a while (had the
wrong mvn versions, and YARN-36) so sounds like this branch isn't
actually being stabilized?

Thanks,
Eli
On Mon, Jul 9, 2012 at 1:31 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
> I'll try and shoot for end of month, but will depend on performance work and how much we'll need to get to parity with hadoop-1.x on branch-2 etc., even though hadoop-0.23 was there. Fingers crossed.
>
> thanks,
> Arun
>
> On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:
>
>> Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha RC?
>>
>> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>> I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.
>>>
>>> Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.
>>>
>>> thanks,
>>> Arun
>>>
>>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>>>
>>>> Folks,
>>>>
>>>> I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>>>>
>>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>>> # RM Restart (MAPREDUCE-4326)
>>>> # Container re-use (MAPREDUCE-3902)
>>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>>>
>>>> If you would like others please set the 'Target Version' and I'll watch that list.
>>>>
>>>> thanks,
>>>> Arun
>>>>
>>>>
>>>> --
>>>> Arun C. Murthy
>>>> Hortonworks Inc.
>>>> http://hortonworks.com/
>>>>
>>>>
>>>
>>> --
>>> Arun C. Murthy
>>> Hortonworks Inc.
>>> http://hortonworks.com/
>>>
>>>
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>

Eli,

 Good point. Looks like both HDFS & MR committers have been lax in maintaining branch-2.1.0-alpha. Lots of stabilization has occurred via branch-2/branch-0.23.

 Since branch-0.23 is nearly there, I'll go ahead and cherry-pick to branch-2.1.0-alpha - do you mind do the same for HDFS from branch-2 also?

thanks,
Arun

On Aug 30, 2012, at 5:43 PM, Eli Collins wrote:

> Hey Arun,
>
> Are you still planning on releasing this branch?  It's been a couple
> of months and branch-2.1.0-alpha wasn't compiling for a while (had the
> wrong mvn versions, and YARN-36) so sounds like this branch isn't
> actually being stabilized?
>
> Thanks,
> Eli
>
>
> On Mon, Jul 9, 2012 at 1:31 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>> I'll try and shoot for end of month, but will depend on performance work and how much we'll need to get to parity with hadoop-1.x on branch-2 etc., even though hadoop-0.23 was there. Fingers crossed.
>>
>> thanks,
>> Arun
>>
>> On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:
>>
>>> Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha RC?
>>>
>>> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>> I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.
>>>>
>>>> Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.
>>>>
>>>> thanks,
>>>> Arun
>>>>
>>>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>>>>
>>>>> Folks,
>>>>>
>>>>> I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>>>>>
>>>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>>>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>>>> # RM Restart (MAPREDUCE-4326)
>>>>> # Container re-use (MAPREDUCE-3902)
>>>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>>>>
>>>>> If you would like others please set the 'Target Version' and I'll watch that list.
>>>>>
>>>>> thanks,
>>>>> Arun
>>>>>
>>>>>
>>>>> --
>>>>> Arun C. Murthy
>>>>> Hortonworks Inc.
>>>>> http://hortonworks.com/
>>>>>
>>>>>
>>>>
>>>> --
>>>> Arun C. Murthy
>>>> Hortonworks Inc.
>>>> http://hortonworks.com/
>>>>
>>>>
>>
>> --
>> Arun C. Murthy
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>>

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

On Fri, Aug 31, 2012 at 8:48 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
> Eli,
>
>  Good point. Looks like both HDFS & MR committers have been lax in maintaining branch-2.1.0-alpha. Lots of stabilization has occurred via branch-2/branch-0.23.
>
>  Since branch-0.23 is nearly there, I'll go ahead and cherry-pick to branch-2.1.0-alpha - do you mind do the same for HDFS from branch-2 also?

Will do, probably won't get to this today early next week with a plan
to spin an RC maybe by the end of week would work?

Thanks,
Eli

>
> thanks,
> Arun
>
> On Aug 30, 2012, at 5:43 PM, Eli Collins wrote:
>
>> Hey Arun,
>>
>> Are you still planning on releasing this branch?  It's been a couple
>> of months and branch-2.1.0-alpha wasn't compiling for a while (had the
>> wrong mvn versions, and YARN-36) so sounds like this branch isn't
>> actually being stabilized?
>>
>> Thanks,
>> Eli
>>
>>
>> On Mon, Jul 9, 2012 at 1:31 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>> I'll try and shoot for end of month, but will depend on performance work and how much we'll need to get to parity with hadoop-1.x on branch-2 etc., even though hadoop-0.23 was there. Fingers crossed.
>>>
>>> thanks,
>>> Arun
>>>
>>> On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:
>>>
>>>> Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha RC?
>>>>
>>>> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>>> I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.
>>>>>
>>>>> Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.
>>>>>
>>>>> thanks,
>>>>> Arun
>>>>>
>>>>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>>>>>
>>>>>> Folks,
>>>>>>
>>>>>> I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>>>>>>
>>>>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>>>>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>>>>> # RM Restart (MAPREDUCE-4326)
>>>>>> # Container re-use (MAPREDUCE-3902)
>>>>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>>>>>
>>>>>> If you would like others please set the 'Target Version' and I'll watch that list.
>>>>>>
>>>>>> thanks,
>>>>>> Arun
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Arun C. Murthy
>>>>>> Hortonworks Inc.
>>>>>> http://hortonworks.com/
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Arun C. Murthy
>>>>> Hortonworks Inc.
>>>>> http://hortonworks.com/
>>>>>
>>>>>
>>>
>>> --
>>> Arun C. Murthy
>>> Hortonworks Inc.
>>> http://hortonworks.com/
>>>
>>>
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>

Should we consider re-branching 2.1.0-alpha off the current branch-2
code, then? Given there's been lots of testing on tip of branch-2, and
not much in there that I consider "scary", it might be easier to do
that than to cherry pick all of the changes individually?

Just a thought.

-Todd

On Fri, Aug 31, 2012 at 9:31 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 31, 2012 at 8:48 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>> Eli,
>>
>>  Good point. Looks like both HDFS & MR committers have been lax in maintaining branch-2.1.0-alpha. Lots of stabilization has occurred via branch-2/branch-0.23.
>>
>>  Since branch-0.23 is nearly there, I'll go ahead and cherry-pick to branch-2.1.0-alpha - do you mind do the same for HDFS from branch-2 also?
>
> Will do, probably won't get to this today early next week with a plan
> to spin an RC maybe by the end of week would work?
>
> Thanks,
> Eli
>
>>
>> thanks,
>> Arun
>>
>> On Aug 30, 2012, at 5:43 PM, Eli Collins wrote:
>>
>>> Hey Arun,
>>>
>>> Are you still planning on releasing this branch?  It's been a couple
>>> of months and branch-2.1.0-alpha wasn't compiling for a while (had the
>>> wrong mvn versions, and YARN-36) so sounds like this branch isn't
>>> actually being stabilized?
>>>
>>> Thanks,
>>> Eli
>>>
>>>
>>> On Mon, Jul 9, 2012 at 1:31 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>> I'll try and shoot for end of month, but will depend on performance work and how much we'll need to get to parity with hadoop-1.x on branch-2 etc., even though hadoop-0.23 was there. Fingers crossed.
>>>>
>>>> thanks,
>>>> Arun
>>>>
>>>> On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:
>>>>
>>>>> Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha RC?
>>>>>
>>>>> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>>>> I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.
>>>>>>
>>>>>> Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.
>>>>>>
>>>>>> thanks,
>>>>>> Arun
>>>>>>
>>>>>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>>>>>>
>>>>>>> Folks,
>>>>>>>
>>>>>>> I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>>>>>>>
>>>>>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>>>>>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>>>>>> # RM Restart (MAPREDUCE-4326)
>>>>>>> # Container re-use (MAPREDUCE-3902)
>>>>>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>>>>>>
>>>>>>> If you would like others please set the 'Target Version' and I'll watch that list.
>>>>>>>
>>>>>>> thanks,
>>>>>>> Arun
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Arun C. Murthy
>>>>>>> Hortonworks Inc.
>>>>>>> http://hortonworks.com/
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Arun C. Murthy
>>>>>> Hortonworks Inc.
>>>>>> http://hortonworks.com/
>>>>>>
>>>>>>
>>>>
>>>> --
>>>> Arun C. Murthy
>>>> Hortonworks Inc.
>>>> http://hortonworks.com/
>>>>
>>>>
>>
>> --
>> Arun C. Murthy
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>>

--
Todd Lipcon
Software Engineer, Cloudera

Makes sense. The only issue is rejiggering fix-versions, CHANGES.txt etc., but I can do that.

My plan to create the RC after 0.23.3 completes the test/integration cycle it's currently in - should be done in the next week or so barring blockers.

thanks,
Arun

On Aug 31, 2012, at 9:40 AM, Todd Lipcon wrote:

> Should we consider re-branching 2.1.0-alpha off the current branch-2
> code, then? Given there's been lots of testing on tip of branch-2, and
> not much in there that I consider "scary", it might be easier to do
> that than to cherry pick all of the changes individually?
>
> Just a thought.
>
> -Todd
>
> On Fri, Aug 31, 2012 at 9:31 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
>> On Fri, Aug 31, 2012 at 8:48 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>> Eli,
>>>
>>> Good point. Looks like both HDFS & MR committers have been lax in maintaining branch-2.1.0-alpha. Lots of stabilization has occurred via branch-2/branch-0.23.
>>>
>>> Since branch-0.23 is nearly there, I'll go ahead and cherry-pick to branch-2.1.0-alpha - do you mind do the same for HDFS from branch-2 also?
>>
>> Will do, probably won't get to this today early next week with a plan
>> to spin an RC maybe by the end of week would work?
>>
>> Thanks,
>> Eli
>>
>>>
>>> thanks,
>>> Arun
>>>
>>> On Aug 30, 2012, at 5:43 PM, Eli Collins wrote:
>>>
>>>> Hey Arun,
>>>>
>>>> Are you still planning on releasing this branch?  It's been a couple
>>>> of months and branch-2.1.0-alpha wasn't compiling for a while (had the
>>>> wrong mvn versions, and YARN-36) so sounds like this branch isn't
>>>> actually being stabilized?
>>>>
>>>> Thanks,
>>>> Eli
>>>>
>>>>
>>>> On Mon, Jul 9, 2012 at 1:31 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>>> I'll try and shoot for end of month, but will depend on performance work and how much we'll need to get to parity with hadoop-1.x on branch-2 etc., even though hadoop-0.23 was there. Fingers crossed.
>>>>>
>>>>> thanks,
>>>>> Arun
>>>>>
>>>>> On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:
>>>>>
>>>>>> Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha RC?
>>>>>>
>>>>>> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>>>>> I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.
>>>>>>>
>>>>>>> Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.
>>>>>>>
>>>>>>> thanks,
>>>>>>> Arun
>>>>>>>
>>>>>>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>>>>>>>
>>>>>>>> Folks,
>>>>>>>>
>>>>>>>> I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>>>>>>>>
>>>>>>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>>>>>>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>>>>>>> # RM Restart (MAPREDUCE-4326)
>>>>>>>> # Container re-use (MAPREDUCE-3902)
>>>>>>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>>>>>>>
>>>>>>>> If you would like others please set the 'Target Version' and I'll watch that list.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> Arun
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Arun C. Murthy
>>>>>>>> Hortonworks Inc.
>>>>>>>> http://hortonworks.com/
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Arun C. Murthy
>>>>>>> Hortonworks Inc.
>>>>>>> http://hortonworks.com/
>>>>>>>
>>>>>>>
>>>>>
>>>>> --
>>>>> Arun C. Murthy
>>>>> Hortonworks Inc.
>>>>> http://hortonworks.com/
>>>>>
>>>>>
>>>
>>> --
>>> Arun C. Murthy
>>> Hortonworks Inc.
>>> http://hortonworks.com/
>>>
>>>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Great, it definitely makes sense on the HDFS side (I was going to
merge in everything from branch-2) so if it makes sense for MR/YARN as
well then let's just cut a new branch and update all the 2.2.0 fixed
jiras to be 2.1.0.

Thanks,
Eli
On Fri, Aug 31, 2012 at 9:45 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
> Makes sense. The only issue is rejiggering fix-versions, CHANGES.txt etc., but I can do that.
>
> My plan to create the RC after 0.23.3 completes the test/integration cycle it's currently in - should be done in the next week or so barring blockers.
>
> thanks,
> Arun
>
> On Aug 31, 2012, at 9:40 AM, Todd Lipcon wrote:
>
>> Should we consider re-branching 2.1.0-alpha off the current branch-2
>> code, then? Given there's been lots of testing on tip of branch-2, and
>> not much in there that I consider "scary", it might be easier to do
>> that than to cherry pick all of the changes individually?
>>
>> Just a thought.
>>
>> -Todd
>>
>> On Fri, Aug 31, 2012 at 9:31 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
>>> On Fri, Aug 31, 2012 at 8:48 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>> Eli,
>>>>
>>>> Good point. Looks like both HDFS & MR committers have been lax in maintaining branch-2.1.0-alpha. Lots of stabilization has occurred via branch-2/branch-0.23.
>>>>
>>>> Since branch-0.23 is nearly there, I'll go ahead and cherry-pick to branch-2.1.0-alpha - do you mind do the same for HDFS from branch-2 also?
>>>
>>> Will do, probably won't get to this today early next week with a plan
>>> to spin an RC maybe by the end of week would work?
>>>
>>> Thanks,
>>> Eli
>>>
>>>>
>>>> thanks,
>>>> Arun
>>>>
>>>> On Aug 30, 2012, at 5:43 PM, Eli Collins wrote:
>>>>
>>>>> Hey Arun,
>>>>>
>>>>> Are you still planning on releasing this branch?  It's been a couple
>>>>> of months and branch-2.1.0-alpha wasn't compiling for a while (had the
>>>>> wrong mvn versions, and YARN-36) so sounds like this branch isn't
>>>>> actually being stabilized?
>>>>>
>>>>> Thanks,
>>>>> Eli
>>>>>
>>>>>
>>>>> On Mon, Jul 9, 2012 at 1:31 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>>>> I'll try and shoot for end of month, but will depend on performance work and how much we'll need to get to parity with hadoop-1.x on branch-2 etc., even though hadoop-0.23 was there. Fingers crossed.
>>>>>>
>>>>>> thanks,
>>>>>> Arun
>>>>>>
>>>>>> On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:
>>>>>>
>>>>>>> Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha RC?
>>>>>>>
>>>>>>> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>>>>>>>> I'm about to create a hadoop-2.0.1-alpha release with a couple of security fixes.
>>>>>>>>
>>>>>>>> Also, I plan to create a branch-2.1.0-alpha for the next release in the hadoop-2 release. So, this way, I can start stabilize that release (performance, bug-fixes etc.) - please be careful, henceforth, while committing to branch-2.1.0-alpha.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> Arun
>>>>>>>>
>>>>>>>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>>>>>>>>
>>>>>>>>> Folks,
>>>>>>>>>
>>>>>>>>> I'm considering cutting a hadoop-2.0.1-alpha release within the next four weeks or so with some more major add ons I think we can get done soon:
>>>>>>>>>
>>>>>>>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and follow-ons as necessary.
>>>>>>>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>>>>>>>> # RM Restart (MAPREDUCE-4326)
>>>>>>>>> # Container re-use (MAPREDUCE-3902)
>>>>>>>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>>>>>>>>
>>>>>>>>> If you would like others please set the 'Target Version' and I'll watch that list.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> Arun
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Arun C. Murthy
>>>>>>>>> Hortonworks Inc.
>>>>>>>>> http://hortonworks.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Arun C. Murthy
>>>>>>>> Hortonworks Inc.
>>>>>>>> http://hortonworks.com/
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Arun C. Murthy

On Aug 31, 2012, at 9:45 AM, Arun C Murthy wrote:

> Makes sense. The only issue is rejiggering fix-versions, CHANGES.txt etc., but I can do that.
>
> My plan to create the RC after 0.23.3 completes the test/integration cycle it's currently in - should be done in the next week or so barring blockers.
>
> thanks,
> Arun
In which case shall we just wipe off 2.1.0-alpha for now and branch out only after 0.23.3's cycle is done. I don't expect major features to go in the meanwhile into branch-2 which we don't want in 2.1.0-alpha.

Thoughts?

Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/

On Fri, Aug 31, 2012 at 12:21 PM, Vinod Kumar Vavilapalli
<[EMAIL PROTECTED]> wrote:
>
> On Aug 31, 2012, at 9:45 AM, Arun C Murthy wrote:
>
> Makes sense. The only issue is rejiggering fix-versions, CHANGES.txt etc.,
> but I can do that.
>
> My plan to create the RC after 0.23.3 completes the test/integration cycle
> it's currently in - should be done in the next week or so barring blockers.
>
> thanks,
> Arun
>
>
>
> In which case shall we just wipe off 2.1.0-alpha for now and branch out only
> after 0.23.3's cycle is done. I don't expect major features to go in the
> meanwhile into branch-2 which we don't want in 2.1.0-alpha.
>

Yea, I think we should nuke 2.1.0-alpha and re-create when we're
actually going to do a release. On the HDFS side there's quite a few
things already waiting to get out, if it's going to take another 4 or
so weeks then would be great to shoot for getting HDFS-3077.

Thanks,
Eli
> Thoughts?
>
> Thanks,
> +Vinod Kumar Vavilapalli
> Hortonworks Inc.
> http://hortonworks.com/
>

On Fri, Aug 31, 2012 at 1:15 PM, Eli Collins <[EMAIL PROTECTED]> wrote:

> Yea, I think we should nuke 2.1.0-alpha and re-create when we're
> actually going to do a release. On the HDFS side there's quite a few
> things already waiting to get out, if it's going to take another 4 or
> so weeks then would be great to shoot for getting HDFS-3077.

Seems doable to me. I'm in the "finishing touches" stages now, and
feeling pretty confident about the basic protocol after a few
machine-years of fault injection testing, plus some early test results
on a 100 node QA setup. After the current round of open JIRAs goes in,
I'll start a sweep for findbugs, removing TODOs, and a adding a few
more stress tests. Then I think it will be a good time to propose a
merge.

-Todd
--
Todd Lipcon
Software Engineer, Cloudera

Hi Arun et.al. I'd still be grateful if you could share what candidates
from 0.23 you would have cherry picked into 2.1.0, maybe the critical ones?
I will need to make this analysis at this point. Pointers would be
appreciated very much.

On Friday, August 31, 2012, Vinod Kumar Vavilapalli wrote:

>
> On Aug 31, 2012, at 9:45 AM, Arun C Murthy wrote:
>
> Makes sense. The only issue is rejiggering fix-versions, CHANGES.txt etc.,
> but I can do that.
>
> My plan to create the RC after 0.23.3 completes the test/integration cycle
> it's currently in - should be done in the next week or so barring blockers.
>
> thanks,
> Arun
>
>
>
> In which case shall we just wipe off 2.1.0-alpha for now and branch out
> only after 0.23.3's cycle is done. I don't expect major features to go in
> the meanwhile into branch-2 which we don't want in 2.1.0-alpha.
>
> Thoughts?
>
> Thanks,
> +Vinod Kumar Vavilapalli
> Hortonworks Inc.
> http://hortonworks.com/
>
>

--
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Per this discussion and the one on common-dev@ w.r.t. version numbers I'm going to start preparing for hadoop-2.0.2 release by fixing versions/CHANGES.txt etc.

I should be able to get an RC out in the next couple of days.

thanks,
Arun

On Sep 6, 2012, at 8:56 PM, Arun C Murthy wrote:

> Per this discussion and the one on common-dev@ w.r.t. version numbers I'm going to start preparing for hadoop-2.0.2 release by fixing versions/CHANGES.txt etc.
>

Starting this work *now*. FYI.

thanks,
Arun

> I should be able to get an RC out in the next couple of days.
>
> thanks,
> Arun

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Yes, I hope to branch and make the RC Tuesday of next week.  There was a
flurry of new issues that came up recently.

I am now waiting on

YARN-60
YARN-66
MAPREDUCE-4612
MAPREDUCE-4611

But I would like to also have in

HDFS-3852
MAPREDUCE-4604
HADOOP-8727

--Bobby

On 8/31/12 11:45 AM, "Arun C Murthy" <[EMAIL PROTECTED]> wrote:

>Makes sense. The only issue is rejiggering fix-versions, CHANGES.txt
>etc., but I can do that.
>
>My plan to create the RC after 0.23.3 completes the test/integration
>cycle it's currently in - should be done in the next week or so barring
>blockers.
>
>thanks,
>Arun
>
>On Aug 31, 2012, at 9:40 AM, Todd Lipcon wrote:
>
>> Should we consider re-branching 2.1.0-alpha off the current branch-2
>> code, then? Given there's been lots of testing on tip of branch-2, and
>> not much in there that I consider "scary", it might be easier to do
>> that than to cherry pick all of the changes individually?
>>
>> Just a thought.
>>
>> -Todd
>>
>> On Fri, Aug 31, 2012 at 9:31 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
>>> On Fri, Aug 31, 2012 at 8:48 AM, Arun C Murthy <[EMAIL PROTECTED]>
>>>wrote:
>>>> Eli,
>>>>
>>>> Good point. Looks like both HDFS & MR committers have been lax in
>>>>maintaining branch-2.1.0-alpha. Lots of stabilization has occurred via
>>>>branch-2/branch-0.23.
>>>>
>>>> Since branch-0.23 is nearly there, I'll go ahead and cherry-pick to
>>>>branch-2.1.0-alpha - do you mind do the same for HDFS from branch-2
>>>>also?
>>>
>>> Will do, probably won't get to this today early next week with a plan
>>> to spin an RC maybe by the end of week would work?
>>>
>>> Thanks,
>>> Eli
>>>
>>>>
>>>> thanks,
>>>> Arun
>>>>
>>>> On Aug 30, 2012, at 5:43 PM, Eli Collins wrote:
>>>>
>>>>> Hey Arun,
>>>>>
>>>>> Are you still planning on releasing this branch?  It's been a couple
>>>>> of months and branch-2.1.0-alpha wasn't compiling for a while (had
>>>>>the
>>>>> wrong mvn versions, and YARN-36) so sounds like this branch isn't
>>>>> actually being stabilized?
>>>>>
>>>>> Thanks,
>>>>> Eli
>>>>>
>>>>>
>>>>> On Mon, Jul 9, 2012 at 1:31 PM, Arun C Murthy <[EMAIL PROTECTED]>
>>>>>wrote:
>>>>>> I'll try and shoot for end of month, but will depend on performance
>>>>>>work and how much we'll need to get to parity with hadoop-1.x on
>>>>>>branch-2 etc., even though hadoop-0.23 was there. Fingers crossed.
>>>>>>
>>>>>> thanks,
>>>>>> Arun
>>>>>>
>>>>>> On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:
>>>>>>
>>>>>>> Thanks Arun, what do you think the ETA is for the first
>>>>>>>2.1.0-alpha RC?
>>>>>>>
>>>>>>> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy
>>>>>>><[EMAIL PROTECTED]> wrote:
>>>>>>>> I'm about to create a hadoop-2.0.1-alpha release with a couple of
>>>>>>>>security fixes.
>>>>>>>>
>>>>>>>> Also, I plan to create a branch-2.1.0-alpha for the next release
>>>>>>>>in the hadoop-2 release. So, this way, I can start stabilize that
>>>>>>>>release (performance, bug-fixes etc.) - please be careful,
>>>>>>>>henceforth, while committing to branch-2.1.0-alpha.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> Arun
>>>>>>>>
>>>>>>>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>>>>>>>>
>>>>>>>>> Folks,
>>>>>>>>>
>>>>>>>>> I'm considering cutting a hadoop-2.0.1-alpha release within the
>>>>>>>>>next four weeks or so with some more major add ons I think we can
>>>>>>>>>get done soon:
>>>>>>>>>
>>>>>>>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd)
>>>>>>>>>and follow-ons as necessary.
>>>>>>>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
>>>>>>>>> # RM Restart (MAPREDUCE-4326)
>>>>>>>>> # Container re-use (MAPREDUCE-3902)
>>>>>>>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
>>>>>>>>>
>>>>>>>>> If you would like others please set the 'Target Version' and
>>>>>>>>>I'll watch that list.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> Arun
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Arun C. Murthy
>>>>>>>>> Hortonworks Inc.
>>>>>>>>> http://hortonworks.com/
>>>>>>>

+1, I was thinking the same thing.

In addition to there having been relatively little testing of 2.1.0-alpha
when compared with the tip of branch-2, I suspect that relatively few folks
would be interested in the rather modest delta between the current
2.0.1-alpha and 2.1.0-alpha.

--
Aaron T. Myers
Software Engineer, Cloudera

On Fri, Aug 31, 2012 at 9:40 AM, Todd Lipcon <[EMAIL PROTECTED]> wrote:

> Should we consider re-branching 2.1.0-alpha off the current branch-2
> code, then? Given there's been lots of testing on tip of branch-2, and
> not much in there that I consider "scary", it might be easier to do
> that than to cherry pick all of the changes individually?
>
> Just a thought.
>
> -Todd
>
> On Fri, Aug 31, 2012 at 9:31 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
> > On Fri, Aug 31, 2012 at 8:48 AM, Arun C Murthy <[EMAIL PROTECTED]>
> wrote:
> >> Eli,
> >>
> >>  Good point. Looks like both HDFS & MR committers have been lax in
> maintaining branch-2.1.0-alpha. Lots of stabilization has occurred via
> branch-2/branch-0.23.
> >>
> >>  Since branch-0.23 is nearly there, I'll go ahead and cherry-pick to
> branch-2.1.0-alpha - do you mind do the same for HDFS from branch-2 also?
> >
> > Will do, probably won't get to this today early next week with a plan
> > to spin an RC maybe by the end of week would work?
> >
> > Thanks,
> > Eli
> >
> >>
> >> thanks,
> >> Arun
> >>
> >> On Aug 30, 2012, at 5:43 PM, Eli Collins wrote:
> >>
> >>> Hey Arun,
> >>>
> >>> Are you still planning on releasing this branch?  It's been a couple
> >>> of months and branch-2.1.0-alpha wasn't compiling for a while (had the
> >>> wrong mvn versions, and YARN-36) so sounds like this branch isn't
> >>> actually being stabilized?
> >>>
> >>> Thanks,
> >>> Eli
> >>>
> >>>
> >>> On Mon, Jul 9, 2012 at 1:31 PM, Arun C Murthy <[EMAIL PROTECTED]>
> wrote:
> >>>> I'll try and shoot for end of month, but will depend on performance
> work and how much we'll need to get to parity with hadoop-1.x on branch-2
> etc., even though hadoop-0.23 was there. Fingers crossed.
> >>>>
> >>>> thanks,
> >>>> Arun
> >>>>
> >>>> On Jul 9, 2012, at 11:59 AM, Eli Collins wrote:
> >>>>
> >>>>> Thanks Arun, what do you think the ETA is for the first 2.1.0-alpha
> RC?
> >>>>>
> >>>>> On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]>
> wrote:
> >>>>>> I'm about to create a hadoop-2.0.1-alpha release with a couple of
> security fixes.
> >>>>>>
> >>>>>> Also, I plan to create a branch-2.1.0-alpha for the next release in
> the hadoop-2 release. So, this way, I can start stabilize that release
> (performance, bug-fixes etc.) - please be careful, henceforth, while
> committing to branch-2.1.0-alpha.
> >>>>>>
> >>>>>> thanks,
> >>>>>> Arun
> >>>>>>
> >>>>>> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
> >>>>>>
> >>>>>>> Folks,
> >>>>>>>
> >>>>>>> I'm considering cutting a hadoop-2.0.1-alpha release within the
> next four weeks or so with some more major add ons I think we can get done
> soon:
> >>>>>>>
> >>>>>>> # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and
> follow-ons as necessary.
> >>>>>>> # Pending security work for YARN (anything for HDFS w.r.t HA?)
> >>>>>>> # RM Restart (MAPREDUCE-4326)
> >>>>>>> # Container re-use (MAPREDUCE-3902)
> >>>>>>> # Multi-resource scheduling for CS (MAPREDUCE-4327).
> >>>>>>>
> >>>>>>> If you would like others please set the 'Target Version' and I'll
> watch that list.
> >>>>>>>
> >>>>>>> thanks,
> >>>>>>> Arun
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Arun C. Murthy
> >>>>>>> Hortonworks Inc.
> >>>>>>> http://hortonworks.com/
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Arun C. Murthy
> >>>>>> Hortonworks Inc.
> >>>>>> http://hortonworks.com/
> >>>>>>
> >>>>>>
> >>>>
> >>>> --
> >>>> Arun C. Murthy
> >>>> Hortonworks Inc.
> >>>> http://hortonworks.com/
> >>>>
> >>>>
> >>
> >> --
> >> Arun C. Murthy
> >> Hortonworks Inc.
> >> http://hortonworks.com/
> >>
> >>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera

I just created branch-2.1.0-alpha.

Please use the 2.2.0-alpha version in jira henceforth for newer features.

thanks,
Arun

Arun,

Thanks for driving this.

If we have them in time, can we count to get the following JIRAs in the
2.1.0-alpha release: MAPREDUCE-4417, HADOOP-8581, HDFS-3637 ?

Thanks.
On Mon, Jul 9, 2012 at 11:55 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:

> I'm about to create a hadoop-2.0.1-alpha release with a couple of security
> fixes.
>
> Also, I plan to create a branch-2.1.0-alpha for the next release in the
> hadoop-2 release. So, this way, I can start stabilize that release
> (performance, bug-fixes etc.) - please be careful, henceforth, while
> committing to branch-2.1.0-alpha.
>
> thanks,
> Arun
>
> On Jun 8, 2012, at 12:08 AM, Arun C Murthy wrote:
>
> > Folks,
> >
> >  I'm considering cutting a hadoop-2.0.1-alpha release within the next
> four weeks or so with some more major add ons I think we can get done soon:
> >
> >  # Auto NN Failover (thanks for the HDFS-3042 merge today Todd) and
> follow-ons as necessary.
> >  # Pending security work for YARN (anything for HDFS w.r.t HA?)
> >  # RM Restart (MAPREDUCE-4326)
> >  # Container re-use (MAPREDUCE-3902)
> >  # Multi-resource scheduling for CS (MAPREDUCE-4327).
> >
> >  If you would like others please set the 'Target Version' and I'll watch
> that list.
> >
> > thanks,
> > Arun
> >
> >
> > --
> > Arun C. Murthy
> > Hortonworks Inc.
> > http://hortonworks.com/
> >
> >
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>
>
--
Alejandro