Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop, mail # dev - Re: Heads up: branch-2.1-beta


Copy link to this message
-
Re: Heads up: branch-2.1-beta
Ralph Castain 2013-06-16, 17:16
HDFS-4866 is marked as a blocker. A patch was submitted and applied, but it only fixes compilation. As I marked on the ticket, the results remain unusable due to linker issues.
On Jun 16, 2013, at 5:33 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:

> Which one are you talking about Ralph? This doesn't show up on any blocker list.
>
> http://s.apache.org/hadoop-blocker-bugs
>
> Arun
>
>
> On Jun 15, 2013, at 4:44 PM, Ralph Castain wrote:
>
>> Not trying to be a pain, but I am trying to get clarification. The protocol buffer support is still broken. Do you intend to release 2.1 with that unfixed?
>>
>>
>> On Jun 15, 2013, at 4:18 PM, Karthik Kambatla <[EMAIL PROTECTED]> wrote:
>>
>>> Re-posting here to the wider audience:
>>>
>>> HADOOP-9517 (Document Hadoop Compatibility): I believe I have incorporated
>>> all suggestions so far. It would be great if people could take another look
>>> at it. I ll iterate fast on any comments so we get this in by the time rest
>>> of the code pieces are committed.
>>>
>>> Thanks
>>> Karthik
>>>
>>>
>>>
>>>
>>> On Sat, Jun 15, 2013 at 11:46 AM, Ralph Castain <[EMAIL PROTECTED]> wrote:
>>>
>>>> Just curious of your procedures. Given that there is at least one blocker
>>>> JIRA out there that has yet to be fully resolved, do you intend to release
>>>> anyway?
>>>>
>>>>
>>>> On Jun 15, 2013, at 8:19 AM, Alejandro Abdelnur <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> If the intention is to get the release out in time for the Hadoop Summit
>>>> we
>>>>> have a very tight schedule.
>>>>>
>>>>> Because the release vote runs for 7 days, we should have an RC latest
>>>>> Monday afternoon, and we should encourage folks to verify & vote ASAP, so
>>>>> if we need to cut a new RC we can do it on Tuesday. Another thing to
>>>>> consider is that if the changes on an RC are corrections that do not
>>>> affect
>>>>> code, we could agree on not reseting the voting period clock if we need
>>>> to
>>>>> cut a new RC (ie doc, build, notes changes).
>>>>>
>>>>> Of the JIRAs in my laundry list for 2.1 the ones I would really want in
>>>> are
>>>>> YARN-752, MAPREDUCE-5171 & YARN-787.
>>>>>
>>>>> The first 2 are already +1ed, the last one needs to be reviewed.
>>>>>
>>>>> I have not committed the first 2 ones yet because I don't want to disrupt
>>>>> things for the folks doing QA.
>>>>>
>>>>> Arun, as you are coordinating the work for this release, please do commit
>>>>> them or give me the go ahead and I'll commit.
>>>>>
>>>>> Also, it  would be great if you can review YARN-787 (as per discussions,
>>>>> the changes on the milli-slot calculations do not affect the current
>>>>> calculations, that would be left for MAPREDUCE-5311 to do).
>>>>>
>>>>> I'll be checking my email over the weekend and I can take care of some
>>>>> stuff if needed (while the monkeys sleep).
>>>>>
>>>>> Thx
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jun 14, 2013 at 9:56 PM, Alejandro Abdelnur <[EMAIL PROTECTED]
>>>>> wrote:
>>>>>
>>>>>> Following is a revisited assessment of JIRAs I would like to get in the
>>>>>> 2.1 release:
>>>>>>
>>>>>> From the 1st group I think all 3 should make.
>>>>>>
>>>>>> From the 2nd group I think YARN-791 should make it for sure and ideally
>>>>>> MAPREDUCE-5130.
>>>>>>
>>>>>> From the 3rd group, I don't think this JIRA will make it.
>>>>>>
>>>>>> From the 4th group, we don't need to worry about this or 2.1
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Alejandro
>>>>>>
>>>>>> ------------------------------------------------------
>>>>>> JIRAs that are in shape to make it to 2.1
>>>>>>
>>>>>> * YARN-752: In AMRMClient, automatically add corresponding rack requests
>>>>>> for requested nodes
>>>>>>
>>>>>> impact: behavior change
>>>>>>
>>>>>> status: patch avail, +1ed.
>>>>>>
>>>>>> * MAPREDUCE-5171: Expose blacklisted nodes from the MR AM REST API
>>>>>>
>>>>>> impact: Addition to MRAM HTTP API
>>>>>>
>>>>>> status: patch avail, +1ed, needs to be committed
>>>>>>
>>>>>> * YARN-787: Remove resource min from Yarn client API