Gera,

 Apologies for the late response, I decided to take the weekend off! *smile*

 Thanks for the feedback, I took a look at your list and here are some 
observations:

On Apr 4, 2014, at 5:06 PM, Gera Shegalov <g...@shegalov.com> wrote:

> I built the release from the rc tag, enabled timeline history service and
> ran a sleep job on a pseudo-distributed cluster.
> 
> I encourage another rc, for 2.4.0 (non-binding)
> 
> 1) Despite the discussion on YARN-1701, timeline AHS still sets
> yarn.timeline-service.generic-application-history.fs-history-store.uri to a
> location under ${hadoop.log.dir} that is meant for local file system, but
> uses it on HDFS by default.

 This is certainly unfortunate, but essentially it's just a bad default config 
value. As such, there is a pretty simple & clear workaround which I'll 
release-doc. 

> 
> 2) Critical patch for WebHdfs/Hftp to fix the filesystem contract HDFS-6143
> is not included


 I had already commented on the jira around the time of RC as you may remember. 
Also, this isn't a regression - this bug has existed for quite a while now. 
Furthermore, there are some back-compatibility concerns we still need to 
address.

> 
> 3) Several patches that already proved themselves useful for diagnostics in
> production and have been available for some months are still not included.
> MAPREDUCE-5044/YARN-1515 is the most obvious example. Our users need to see
> where the task container JVM got stuck when it was timed out by AM.

 Please accept my personal apologies, this wasn't on my radar to review. In 
future, pls drop me a note if you don't see any activity on a jira you care 
about - I'm sure others like Vinod, Jason etc. would love to help too; it's 
just something that got missed by the community collectively. Having said that, 
as you can imagine, new features cannot be a blocker to a release; this sets up 
a dynamic where it's impossible to please everyone and we cannot ship any 
release… as you may have seen it's been quite an effort for the last 3-4 weeks 
just to corral everyone into fixing/reviewing/committing blocker bugs itself. 
*smile*

 Overall, please feel free to share your feedback, but the above list doesn't 
seem to have a critically bad release blocker. 
 
 Also, I plan to follow up with a 2.4.1 in a couple of weeks; I'll make sure to 
include as much as your list as possible - and future ones.

thanks,
Arun

> 
> Thanks,
> 
> Gera
> 
> 
> 
> 
> On Fri, Apr 4, 2014 at 3:51 PM, Azuryy <azury...@gmail.com> wrote:
> 
>> Arun,
>> 
>> Do you mean you will cut another RC for 2.4?
>> 
>> 
>> Sent from my iPhone5s
>> 
>>> On 2014年4月5日, at 3:50, "Arun C. Murthy" <a...@hortonworks.com> wrote:
>>> 
>>> Thanks for helping Tsuyoshi. Pls mark them as Blockers and set the
>> fix-version to 2.4.1.
>>> 
>>> Thanks again.
>>> 
>>> Arun
>>> 
>>> 
>>>> On Apr 3, 2014, at 11:38 PM, Tsuyoshi OZAWA <ozawa.tsuyo...@gmail.com>
>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> Updated a test result log based on the result of 2.4.0-rc0:
>>>> https://gist.github.com/oza/9965197
>>>> 
>>>> IMO, there are some blockers to be fixed:
>>>> * MAPREDUCE-5815(TestMRAppMaster failure)
>>>> * YARN-1872(TestDistributedShell failure)
>>>> * HDFS: TestSymlinkLocalFSFileSystem failure on Linux (I cannot find
>>>> JIRA about this failure)
>>>> 
>>>> Now I'm checking the problem reported by Azuryy.
>>>> 
>>>> Thanks,
>>>> - Tsuyoshi
>>>> 
>>>>> On Fri, Apr 4, 2014 at 8:55 AM, Tsuyoshi OZAWA <
>> ozawa.tsuyo...@gmail.com> wrote:
>>>>> Hi,
>>>>> 
>>>>> Ran tests and confirmed that some tests(TestSymlinkLocalFSFileSystem)
>> fail.
>>>>> The log of the test failure is as follows:
>>>>> 
>>>>> https://gist.github.com/oza/9965197
>>>>> 
>>>>> Should we fix or disable the feature?
>>>>> 
>>>>> Thanks,
>>>>> - Tsuyoshi
>>>>> 
>>>>>> On Mon, Mar 31, 2014 at 6:22 PM, Arun C Murthy <a...@hortonworks.com>
>> wrote:
>>>>>> Folks,
>>>>>> 
>>>>>> I've created a release candidate (rc0) for hadoop-2.4.0 that I would
>> like to get released.
>>>>>> 
>>>>>> The RC is available at:
>> http://people.apache.org/~acmurthy/hadoop-2.4.0-rc0
>>>>>> The RC tag in svn is here:
>> https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.4.0-rc0
>>>>>> 
>>>>>> The maven artifacts are available via repository.apache.org.
>>>>>> 
>>>>>> Please try the release and vote; the vote will run for the usual 7
>> days.
>>>>>> 
>>>>>> thanks,
>>>>>> Arun
>>>>>> 
>>>>>> --
>>>>>> Arun C. Murthy
>>>>>> Hortonworks Inc.
>>>>>> http://hortonworks.com/
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> CONFIDENTIALITY NOTICE
>>>>>> NOTICE: This message is intended for the use of the individual or
>> entity to
>>>>>> which it is addressed and may contain information that is
>> confidential,
>>>>>> privileged and exempt from disclosure under applicable law. If the
>> reader
>>>>>> of this message is not the intended recipient, you are hereby
>> notified that
>>>>>> any printing, copying, dissemination, distribution, disclosure or
>>>>>> forwarding of this communication is strictly prohibited. If you have
>>>>>> received this communication in error, please contact the sender
>> immediately
>>>>>> and delete it from your system. Thank You.
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> - Tsuyoshi
>>>> 
>>>> 
>>>> 
>>>> --
>>>> - Tsuyoshi
>>> 
>>> --
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity
>> to
>>> which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified
>> that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender
>> immediately
>>> and delete it from your system. Thank You.
>> 

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



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Reply via email to