Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <546BE99B.9080505@oss.nttdata.co.jp>
Date: Wed, 19 Nov 2014 09:51:39 +0900
From: Masatake Iwasaki <iwasakims@oss.nttdata.co.jp>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: common-dev@hadoop.apache.org,
 "yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>
CC: "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
 "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>
Subject: Re: [VOTE] Release Apache Hadoop 2.6.0
References: <032A4450-D9EF-4BD8-B510-A21253D7D771@hortonworks.com>
	<2146515069.768198.1416329269937.JavaMail.yahoo@jws10787.mail.gq1.yahoo.com>
	<CAF0xP8zY0t7ity5MhHXthbyzM-56X=sUw+ocmcUHDTFittdVGQ@mail.gmail.com>
	<CALwhT96byY88SZaMTZKtUbPz6O5X=Pc7ANwAPc30gX8Rj8dcNA@mail.gmail.com>
 <CAAD07OJdHD3TQio--ja1NYyS7GwAvipTh0XEf4Xq9UsSJJg5Zw@mail.gmail.com>
In-Reply-To: 
 <CAAD07OJdHD3TQio--ja1NYyS7GwAvipTh0XEf4Xq9UsSJJg5Zw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

+1 (non-binding)

+ built from source tarball
+ ran some example jobs in HiBench such as
   nutchindexing, wordcount, dfsioe, hivebench, kmeans, pagerank, bayes, sort, terasort
   on 3 node cluster.

I'm on the same side with Tsuyoshi and would like HDFS-6833 to be fixed in 2.6.1 at least.

Masatake Iwasaki

(11/19/14, 7:41), Tsuyoshi OZAWA wrote:
> +1 if once discussion about HDFS-6833 is done(non-binding).
>
> * Verified checksum.
> * Deployed cluster and ran some mr examples.
> * Checked RM restart while running jobs.
>
>>   I think you have to pass along -Pdist too… afaik that is how the Jenkins we use for building release artifacts operates.
>
> Thanks for your comment, Arun. It's still fails with -Pdist option. It
> can be environment-depend problem. +1 for fixing at 2.6.1.
>
> Thanks,
> - Tsuyoshi
>
> On Wed, Nov 19, 2014 at 5:04 AM, Karthik Kambatla <kasha@cloudera.com> wrote:
>> +1 (binding) on the source tarball, would be nice to redo the binary
>> tarball.
>>
>> - Stood up a pseudo-dist cluster, and ran some HDFS and MR jobs.
>> - The binary is about 40 MB larger than the previous release; it appears
>> the docs are copied over twice - share/doc/hadoop and share/hadoop. The
>> binary tarball from the release build should have everything in the right
>> place, I can help with this if needed.
>> - index.html (under share/doc/hadoop) is stale, and could be updated. If we
>> ship the bits as is, we should at least put the new features on the
>> website. Also, highlight the alpha features (like YARN reservations) as
>> alpha.
>>
>> Thanks for putting this together, Arun.
>>
>> Karthik
>>
>> On Tue, Nov 18, 2014 at 11:07 AM, Jian He <jhe@hortonworks.com> wrote:
>>
>>> +1,
>>>
>>> Built from source.
>>> Deployed a single node cluster.
>>> Ran sample MapReduce jobs while restarting RM successfully.
>>>
>>> Jian
>>>
>>> On Tue, Nov 18, 2014 at 8:47 AM, Eric Payne <erichadoop-1@yahoo.com.invalid
>>>>
>>> wrote:
>>>
>>>> +1 . Thanks Arun, for producing this release. I downloaded and built
>>>> the source. I started local cluster and ran wordcount, sleep, and
>>> streaming
>>>> jobs.
>>>>
>>>>   - I ran a distributed shell job which tested preserving containers
>>> across
>>>> AM restart by setting the -keep_containers_across_application_attempts
>>> flag
>>>> and killing the first AM once the containers start. I checked the results
>>>> by looking in the timeline server and comparing the start times of the
>>>> non-AM containers against the start times of the later AM container. -
>>>> I enabled the preemption feature and verified containers were preempted
>>> and
>>>> queues were adjusted to guaranteed levels.
>>>> - I ran unit tests for hadoop-yarn-server-resourcemanage. All passed with
>>>> the exception of TestContainerResourceUsage. - I ran unit tests for
>>>> hadoop-hdfs. All passed with the exception of
>>>> TestBPOfferService#testBasicFunctionality (HDFS-3930) Thank you,-Eric
>>> Payne
>>>>
>>>>
>>>>
>>>>
>>>>        From: Arun C Murthy <acm@hortonworks.com>
>>>>   To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>; "
>>>> hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>; "
>>>> yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>; "
>>>> mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
>>>>   Sent: Thursday, November 13, 2014 5:08 PM
>>>>   Subject: [VOTE] Release Apache Hadoop 2.6.0
>>>>
>>>> Folks,
>>>>
>>>> I've created another release candidate (rc1) for hadoop-2.6.0 based on
>>> the
>>>> feedback.
>>>>
>>>> The RC is available at:
>>>> http://people.apache.org/~acmurthy/hadoop-2.6.0-rc1
>>>> The RC tag in git is: release-2.6.0-rc1
>>>>
>>>> The maven artifacts are available via repository.apache.org at
>>>> https://repository.apache.org/content/repositories/orgapachehadoop-1013.
>>>>
>>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>>
>>>> thanks,
>>>> Arun
>>>>
>>>>
>>>> --
>>>> 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.
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> 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.
>>>
>
>
>