As I mentioned on the JIRA, I also ran into it just once. I didn't have the time to investigate, and just wanted to see if anyone else also ran into it. If it is a rare occurrence, I am fine with going through with the release.
I have some naming reservations against calling 2.7.0 an alpha. I am fine with having a 2.7.0-alpha release, followed by 2.7.0-beta and 2.7.0 GA. Calling 2.7.0 alpha and 2.7.1 GA somehow doesn't seem right. I know we followed that for 2.0.0, but it didn't make much sense to me or many others I know (even outside Cloudera). How about we skip this all entirely? If the HDFS issues reported aren't going to render the cluster unusable, we could just release 2.7.0 and mark it current/latest. We can move the stable tag to 2.7.1 or 2.7.2 whichever version deserves the bit. On Mon, Apr 20, 2015 at 11:10 AM, Vinod Kumar Vavilapalli < vino...@hortonworks.com> wrote: > Yup, missed this. Tx for bumping up. > > I did run simple MR jobs & dist-shell on my Mac. Things worked fine. > > Brahma Reddy also commented on YARN-3492 saying that he could take > Karthik's configs and run jobs successfully. So, I moved it out to 2.7.1, > it's likely an environment issue. Karthik, please look at the JIRA. > > Thanks > +Vinod > > On Apr 17, 2015, at 10:49 AM, Tsuyoshi Ozawa <oz...@apache.org> wrote: > > > Hi Vinod, > > > > Could you check a comment by Karthik? Maybe you're missing it. > > > >> Stood up a pseudo-dist cluster using the binary bits and ran a pi job. > >> - The MR-AM got allocated, but never launched because the NM-RM didn't > talk > >> to each other. Filed YARN-3492. Was able to run jobs after restart. > >> > >> I believe we should at least investigate this further to see what could > >> have been going on. > > > > Thanks, > > - Tsuyoshi > > > > On Fri, Apr 17, 2015 at 12:47 PM, Tsuyoshi Ozawa <oz...@apache.org> > wrote: > >> I'd like to agree with Vinod's suggestion. > >> > >> Thanks, > >> - Tsuyoshi > >> > >> On Fri, Apr 17, 2015 at 9:12 AM, Vinod Kumar Vavilapalli > >> <vino...@hortonworks.com> wrote: > >>> Quick look tells me this is a bug that needs fixing. > >>> > >>> Am on the road, so couldn't close the vote right after 5 days. > >>> > >>> Seeing as this is coming up beyond the voting period, unless you feel > strongly against it, I'd like to close the vote as a success but do the > following: call this release an alpha for downstream consumption in line > with my original proposal, following it up with a 2.7.1 in two weeks. > >>> > >>> Thanks > >>> +Vinod > >>> > >>> On Apr 17, 2015, at 2:27 AM, Colin P. McCabe <cmcc...@apache.org> > wrote: > >>> > >>>> I would like to fix HDFS-8070, which just came to light. The impact > >>>> is that if this isn't fixed, 2.6 clients will be unable to do > >>>> short-circuit reads against 2.7 datanodes. > >>>> > >>>> best, > >>>> Colin > >>>> > >>>> On Wed, Apr 15, 2015 at 8:19 PM, Brahma Reddy Battula > >>>> <brahmareddy.batt...@huawei.com> wrote: > >>>>> Need Jcardar changes to support java 7 Byte code..I will work along > with Todd to get jcardar.. > >>>>> > >>>>> Thanks & Regards > >>>>> Brahma Reddy Battula > >>>>> ________________________________________ > >>>>> From: Vinod Kumar Vavilapalli [vino...@hortonworks.com] > >>>>> Sent: Wednesday, April 15, 2015 6:29 PM > >>>>> To: common-dev@hadoop.apache.org > >>>>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.0 RC0 > >>>>> > >>>>> Tx Brahma. Apologies for missing your offline email. > >>>>> > >>>>> So, did you have luck with an updated JCarder? Or does that need > JCarder changes that you are waiting on. > >>>>> > >>>>> +Vinod > >>>>> > >>>>> On Apr 15, 2015, at 7:21 AM, Brahma Reddy Battula < > brahmareddy.batt...@huawei.com> wrote: > >>>>> > >>>>>> HI Allen > >>>>>> > >>>>>> Thanks for updating here [ HDFS-8132 ].. > >>>>>> > >>>>>> Jcardar is tied to the Java 6 class format. Hadoop 2.7.0 is our > first release that compiled Java 7 class files. Jcarder needs to updated to > support Java 7 byte code.. > >>>>>> > >>>>>> > >>>>>> I am +1 ( non binding),, after all the regression tests passed > against 2.7.0-RC0 > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> Thanks & Regards > >>>>>> Brahma Reddy Battula > >>>>>> ________________________________________ > >>>>>> From: Allen Wittenauer [a...@altiscale.com] > >>>>>> Sent: Wednesday, April 15, 2015 12:45 AM > >>>>>> To: common-dev@hadoop.apache.org > >>>>>> Cc: hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org; > mapreduce-...@hadoop.apache.org > >>>>>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.0 RC0 > >>>>>> > >>>>>> Someone should look into HDFS-8132, which appears to have been > filed against RC0. > >>>>>> > >>>>>> On Apr 11, 2015, at 1:44 AM, Vinod Kumar Vavilapalli < > vino...@apache.org> wrote: > >>>>>> > >>>>>>> Hi all, > >>>>>>> > >>>>>>> I've created a release candidate RC0 for Apache Hadoop 2.7.0. > >>>>>>> > >>>>>>> The RC is available at: > http://people.apache.org/~vinodkv/hadoop-2.7.0-RC0/ > >>>>>>> > >>>>>>> The RC tag in git is: release-2.7.0-RC0 > >>>>>>> > >>>>>>> The maven artifacts are available via repository.apache.org at > >>>>>>> > https://repository.apache.org/content/repositories/orgapachehadoop-1017/ > >>>>>>> > >>>>>>> As discussed before > >>>>>>> - This release will only work with JDK 1.7 and above > >>>>>>> - I’d like to use this as a starting release for 2.7.x [1], > depending on > >>>>>>> how it goes, get it stabilized and potentially use a 2.7.1 in a few > >>>>>>> weeks as the stable release. > >>>>>>> > >>>>>>> Please try the release and vote; the vote will run for the usual 5 > days. > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Vinod > >>>>>>> > >>>>>>> [1]: A 2.7.1 release to follow up 2.7.0 > >>>>>>> http://markmail.org/thread/zwzze6cqqgwq4rmw > >>>>>> > >>>>> > >>> > > -- Karthik Kambatla Software Engineer, Cloudera Inc. -------------------------------------------- http://five.sentenc.es
