Re: [VOTE] Merge yarn-native-services branch into trunk

> On Sep 5, 2017, at 2:53 PM, Jian He wrote: > >> Based on the documentation, this doesn’t appear to be a fully function DNS >> server as an admin would expect (e.g., BIND, Knot, whatever). Where’s >> forwarding? How do I setup notify? Are secondaries even supported?

Re: [VOTE] Merge yarn-native-services branch into trunk

2) Lots of markdown problems in the NativeServicesDiscovery.md document. This includes things like Œyarnsite.xml¹ (missing a dash.) The md patch uploaded to YARN-5244 had some special chars. I fixed those in YARN-7161. > -

Re: [VOTE] Merge yarn-native-services branch into trunk

+1 (binding). Cheers -Arun On Fri, Sep 1, 2017 at 5:24 PM, Wangda Tan wrote: > +1 (Binding), I tried to use YARN service assembly before to run different > kinds of jobs (for example, distributed Tensorflow), it is really easy for > end user to run jobs on YARN. > > Thanks

Re: [DISCUSS] Merge yarn-native-services branch into trunk

Thanks for all the work on this folks. I know the VOTE thread has started for this. But I did have a couple of questions: * Is there a branch-2 merge planned for this ? * I understand YARN-7126 has some introductory documentation, But I think we need to flesh it up a bit more before release, I

Re: Apache Hadoop 2.8.2 Release Plan

I assume the quiet over the holiday means we agreed to move forward without taking HADOOP-14439 into 2.8.2. There is a new release building (docker based) issue could be related to HADOOP-14474 where we removed oracle java 7 installer due to recent download address/contract change by Oracle.

Re: [VOTE] Merge yarn-native-services branch into trunk

> On Aug 31, 2017, at 8:33 PM, Jian He wrote: > I would like to call a vote for merging yarn-native-services to trunk. 1) Did I miss it or is there no actual end-user documentation on how to use this? I see

Re: [VOTE] Merge yarn-native-services branch into trunk

> 1) Did I miss it or is there no actual end-user documentation on how to use > this? Yes, we are in the process of finishing up the the doc and posting it. We considered this a release blocker for 3.0.0-beta1 and so working on it in parallel while the branch merge happens. > 2) Lots

Re: [VOTE] Merge yarn-native-services branch into trunk

> On Sep 5, 2017, at 3:12 PM, Gour Saha wrote: > > 2) Lots of markdown problems in the NativeServicesDiscovery.md document. > This includes things like Œyarnsite.xml¹ (missing a dash.) > > The md patch uploaded to YARN-5244 had some special chars. I fixed those > in

Re: [VOTE] Merge yarn-native-services branch into trunk

Thanks Allen. You are right, the github renderer does have trouble rendering the headers. I was only looking at the html generated by mvn site, which did not have trouble rendering them. Anyway I added a space after all the hashes and it looks ok through github now. -Gour On 9/5/17, 3:20 PM,

[jira] [Resolved] (MAPREDUCE-6941) The default setting doesn't work for MapReduce job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved MAPREDUCE-6941. Resolution: Not A Problem I'm going to close this based on Ray's analysis. Junping, if

Re: [DISCUSS] Looking to a 2.9.0 release

Hi Subru, Thanks for starting the discussion. We are targeting merging YARN-5734 (API-based scheduler configuration) to branch-2 before the release of 2.9.0, since the feature is close to complete. Regarding the requirements for merge, 1. API compatibility - this feature adds new APIs, does not

Re: [VOTE] Merge yarn-native-services branch into trunk

> If it doesn’t have all the bells and whistles, then it shouldn’t be on > port 53 by default. Sure, I’ll change the default port to not use 53 and document it. > *how* is it getting launched on a privileged port? It sounds like the > expectation is to run “command” as root. *ALL*

Re: DISCUSS: Hadoop Compatability Guidelines

Good idea.  I should have thought of that. :)  Done. Daniel On 9/5/17 10:33 AM, Anu Engineer wrote: Could you please attach the PDFs to the JIRA. I think the mailer is stripping them off from the mail. Thanks Anu On 9/5/17, 9:44 AM, "Daniel Templeton" wrote:

Re: DISCUSS: Hadoop Compatability Guidelines

Resending with a broader audience, and reattaching the PDFs. Daniel On 9/4/17 9:01 AM, Daniel Templeton wrote: All, in prep for Hadoop 3 beta 1 I've been working on updating the compatibility guidelines on HADOOP-13714.  I think the initial doc is more or less complete, so I'd like to open

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/514/ [Sep 4, 2017 2:41:02 PM] (varunsaxena) YARN-7152. [ATSv2] Registering timeline client before AMRMClient service [Sep 5, 2017 2:36:43 AM] (sunilg) YARN-7022. Improve click interaction in queue topology in

Re: DISCUSS: Hadoop Compatability Guidelines

Could you please attach the PDFs to the JIRA. I think the mailer is stripping them off from the mail. Thanks Anu On 9/5/17, 9:44 AM, "Daniel Templeton" wrote: >Resending with a broader audience, and reattaching the PDFs. > >Daniel > >On 9/4/17 9:01 AM, Daniel

Re: DISCUSS: Hadoop Compatability Guidelines

Thanks for starting this Daniel. I think we should also add a section for store compatibility (all state stores including RM, NM, Federation etc.). Essentially an explicit policy detailing when is it ok to change the major and minor versions and how it should relate to the hadoop release version.