Re: YARN Contributor Meetup

Gentle reminder: please mark all the timings that work for you. So far, we have 9 people interested. http://doodle.com/poll/hu678caa7wbeeqvw On Mon, Jul 25, 2016 at 11:28 AM, Karthik Kambatla wrote: > Hi folks > > Per our previous discussions, Cloudera would like to host

[jira] [Created] (YARN-5447) Consider including allocationRequestId in NMContainerStatus to allow recovery in case of RM failover

Subru Krishnan created YARN-5447: Summary: Consider including allocationRequestId in NMContainerStatus to allow recovery in case of RM failover Key: YARN-5447 URL: https://issues.apache.org/jira/browse/YARN-5447

Re: [DISCUSS] Release numbering semantics with concurrent (>2) releases [Was Setting JIRA fix versions for 3.0.0 releases]

I've written up the proposal from my initial reply in a GDoc. I found one bug in the rules when working through my example again, and also incorporated Akira's correction. Thanks all for the discussion so far! https://docs.google.com/document/d/1vlDtpsnSjBPIZiWQjSwgnV0_Z6ZQJ1r91J8G0FduyTg/edit

Re: Heads up: branched branch-3.0.0-alpha1

Looking at the state of branch-3.0.0-alpha1 and the fix versions, we're already out of sync. I think the easiest solution is to (close to the release date) rebranch and change any 3.0.0-alpha2 fix versions to 3.0.0-alpha1. I think the versioning discussions are converging, so hopefully soon. I'll

Re: [DISCUSS] Release numbering semantics with concurrent (>2) releases [Was Setting JIRA fix versions for 3.0.0 releases]

Inline. > >> BTW, I never see we have a clear definition for alpha release. It is >> previously used as unstable in API definition (2.1-alpha, 2.2-alpha, etc.) >> but sometimes means unstable in production quality (2.7.0). I think we >> should clearly define it with major consensus so user won't

[jira] [Created] (YARN-5446) Find a bug when clicking hadoop icon(in the left top corner) in cluster overview page

Chen Ge created YARN-5446: - Summary: Find a bug when clicking hadoop icon(in the left top corner) in cluster overview page Key: YARN-5446 URL: https://issues.apache.org/jira/browse/YARN-5446 Project: Hadoop

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/31/ [Jul 21, 2016 3:38:20 AM] (lei) HADOOP-12928. Update netty to 3.10.5.Final to sync with zookeeper. (lei) [Jul 21, 2016 6:50:47 AM] (rohithsharmaks) YARN-1126. Add validation of users input nodes-states

[jira] [Created] (YARN-5445) Log aggregation configured to different namenode can fail fast

Chackaravarthy created YARN-5445: Summary: Log aggregation configured to different namenode can fail fast Key: YARN-5445 URL: https://issues.apache.org/jira/browse/YARN-5445 Project: Hadoop YARN

[jira] [Created] (YARN-5444) TestLinuxContainerExecutorWithMocks failed due to unstable assumption.

Yufei Gu created YARN-5444: -- Summary: TestLinuxContainerExecutorWithMocks failed due to unstable assumption. Key: YARN-5444 URL: https://issues.apache.org/jira/browse/YARN-5444 Project: Hadoop YARN

Job Preserving AM and NM code parts

Hi All, I am trying to understand the code flow and the parts of code which deal with the job preservation for AMs and NMs. Can anyone point me to relevant resources and/or code pointers please? I am referring to YARN-1489 but would appreciate more deeper pointers. Regards, Atri -- Regards,

[jira] [Created] (YARN-5443) Add support for docker inspect

Shane Kumpf created YARN-5443: - Summary: Add support for docker inspect Key: YARN-5443 URL: https://issues.apache.org/jira/browse/YARN-5443 Project: Hadoop YARN Issue Type: Sub-task

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/116/ [Jul 27, 2016 10:41:09 AM] (aajisaka) HADOOP-9427. Use JUnit assumptions to skip platform-specific tests. [Jul 27, 2016 8:58:04 PM] (yzhang) HDFS-10667. Report more accurate info about data corruption