Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

+1 (binding) Did the basic checks and ran against a single node local setup. — Hitesh On Jan 14, 2016, at 8:57 PM, Vinod Kumar Vavilapalli wrote: > Hi all, > > I've created an updated release candidate RC2 for Apache Hadoop 2.7.2. > > As discussed before, this is the

Re: YARN replica selection

Moving conversation to yarn-dev. BCC’ed hdfs-dev. YARN actually does not do anything except give back containers based on what an application requested for. It is up to each and every application to first figure out where the data is located and then make optimal choices based on which node to

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

There are a couple of different approaches we could take. How about publishing/releasing bits such as “2.8.0-RC0”. Downstream projects can depend on these and use them normally similar to the approach that they would have taken with release 2.8.0 or 2.8.0-alpha. After some baking ( or more RC

Re: [VOTE] Release Apache Hadoop 2.6.0

+1 (binding) Built Hadoop from source, compiled Tez against the hadoop jars pushed to staging repo and ran a few example Tez jobs on a single node cluster. — HItesh On Nov 13, 2014, at 3:08 PM, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created another release candidate

Re: [VOTE] Migration from subversion to git for version control

+1 — Hitesh On Aug 8, 2014, at 7:57 PM, Karthik Kambatla ka...@cloudera.com wrote: I have put together this proposal based on recent discussion on this topic. Please vote on the proposal. The vote runs for 7 days. 1. Migrate from subversion to git for version control. 2.

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

+1 (binding) — Hitesh On Jun 24, 2014, at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will

Re: [VOTE] Release Apache Hadoop 2.2.0

+1. Built from source and ran distributed shell along with simple MR jobs on a single node cluster. -- HItesh On Oct 7, 2013, at 12:00 AM, Arun C Murthy wrote: Folks, I've created a release candidate (rc0) for hadoop-2.2.0 that I would like to get released - this release fixes a small

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

Hi Arun, From a YARN perspective, YARN-791 and YARN-727 are 2 jiras that may potentially change the apis. They can implemented in a backward compat fashion if committed after 2.1.0. However, this will require adding of differently-named apis ( different urls in case of the webservices ) and

Re: [VOTE] Release Apache Hadoop 0.23.8

+1 (non-binding) Built from source, ran some basic tests on a single node cluster. -- Hitesh On May 28, 2013, at 9:00 AM, Thomas Graves wrote: I've created a release candidate (RC0) for hadoop-0.23.8 that I would like to release. This release is a sustaining release with several

Re: [VOTE] Release Apache Hadoop 0.23.7

+1. Downloaded source, built and ran a couple of sample jobs on a single node cluster. -- Hitesh On Apr 11, 2013, at 12:55 PM, Thomas Graves wrote: I've created a release candidate (RC0) for hadoop-0.23.7 that I would like to release. This release is a sustaining release with several

Re: [VOTE] Release Apache Hadoop 2.0.4-alpha

+1 (non-binding). Downloaded from source, tested distributed shell and simple MR jobs on a single-node cluster. -- Hitesh On Apr 12, 2013, at 2:56 PM, Arun C Murthy wrote: Folks, I've created a release candidate (RC2) for hadoop-2.0.4-alpha that I would like to release. The RC is

Re: [VOTE] Release hadoop-2.0.3-alpha

+1 (non-binding) Downloaded ( verified checksums ) and built from source, deployed and successfully ran both MR and distributed shell examples. -- Hitesh On Feb 6, 2013, at 7:59 PM, Arun C Murthy wrote: Folks, I've created a release candidate (rc0) for hadoop-2.0.3-alpha that I would

[jira] [Created] (HDFS-3409) Secondary namenode should expose checkpoint info via JMX

Hitesh Shah created HDFS-3409: - Summary: Secondary namenode should expose checkpoint info via JMX Key: HDFS-3409 URL: https://issues.apache.org/jira/browse/HDFS-3409 Project: Hadoop HDFS Issue

[jira] [Created] (HDFS-2816) Fix missing license header in hadoop-hdfs-project/hadoop-hdfs-httpfs/dev-support/findbugsExcludeFile.xml

/browse/HDFS-2816 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Priority: Trivial Fix For: 0.24.0, 0.23.1 -- This message is automatically generated by JIRA. If you think it was sent

[jira] [Created] (HDFS-2814) NamenodeMXBean does not account for svn revision in the version information

Issue Type: Improvement Affects Versions: 1.0.0, 0.23.0 Reporter: Hitesh Shah Priority: Minor Fix For: 0.23.1, 1.1.0 Unlike the jobtracker where both the UI and jmx information report the version as x.y.z, rsvn revision, in case of the namenode, the UI