Apache Hadoop qbt Report: trunk+JDK8 on Windows/x64

For more details, see https://builds.apache.org/job/hadoop-trunk-win/476/ [May 22, 2018 2:27:08 PM] (jlowe) YARN-8206. Sending a kill does not immediately kill docker containers. [May 22, 2018 4:20:51 PM] (kihwal) HADOOP-15450. Avoid fsync storm triggered by DiskChecker and handle disk [May 22,

[jira] [Created] (YARN-8352) AM should retry on a different node after the previous application attempt fail

Zhizhen Hou created YARN-8352: - Summary: AM should retry on a different node after the previous application attempt fail Key: YARN-8352 URL: https://issues.apache.org/jira/browse/YARN-8352 Project:

[jira] [Created] (YARN-8351) RM is flooded with node attributes manager logs

Weiwei Yang created YARN-8351: - Summary: RM is flooded with node attributes manager logs Key: YARN-8351 URL: https://issues.apache.org/jira/browse/YARN-8351 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-8350) NPE in service AM related to placement policy

Billie Rinaldi created YARN-8350: Summary: NPE in service AM related to placement policy Key: YARN-8350 URL: https://issues.apache.org/jira/browse/YARN-8350 Project: Hadoop YARN Issue Type:

Re: Apache Hadoop 3.0.3 Release plan

Thanks Eric. Sounds good. I may try to see if I can do the branching/RC sooner. --Yongjun On Wed, May 23, 2018 at 2:18 PM, Eric Badger wrote: > My thinking is to cut the branch in next couple of days and create RC for > vote at the end of month. > > We plan to cut

Re: Apache Hadoop 3.0.3 Release plan

My thinking is to cut the branch in next couple of days and create RC for vote at the end of month. > We plan to cut branch-3.0.3 by the coming Wednesday (May 9th) and vote for RC on May 30th I much prefer to wait to cut the branch until just before the production of the release and the vote.

Re: Apache Hadoop 3.0.3 Release plan

Hi, I have gardened the jiras for 3.0.3, and have the following open issues: https://issues.apache.org/jira/issues/?filter=12343970 Two of them are blockers, one of them (YARN-8346) has already got +1 for patch, the other (YARN-8108) will take longer time to resolve and it seems we can possibly

[jira] [Created] (YARN-8349) Remove YARN registry entries when a service is killed by the RM

Shane Kumpf created YARN-8349: - Summary: Remove YARN registry entries when a service is killed by the RM Key: YARN-8349 URL: https://issues.apache.org/jira/browse/YARN-8349 Project: Hadoop YARN

[jira] [Resolved] (YARN-8334) [GPG] Fix potential connection leak in GPGUtils

[ https://issues.apache.org/jira/browse/YARN-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang resolved YARN-8334. Resolution: Fixed > [GPG] Fix potential connection leak in GPGUtils >

[jira] [Created] (YARN-8348) Incorrect and missing AfterClass in HBase-tests

Giovanni Matteo Fumarola created YARN-8348: -- Summary: Incorrect and missing AfterClass in HBase-tests Key: YARN-8348 URL: https://issues.apache.org/jira/browse/YARN-8348 Project: Hadoop YARN

[jira] [Created] (YARN-8347) [Umbrella] Upgrade efforts to Hadoop 3.x

Sunil Govindan created YARN-8347: Summary: [Umbrella] Upgrade efforts to Hadoop 3.x Key: YARN-8347 URL: https://issues.apache.org/jira/browse/YARN-8347 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

Rohith Sharma K S created YARN-8346: --- Summary: Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full" Key: YARN-8346 URL: https://issues.apache.org/jira/browse/YARN-8346

YARN-8320 CPU isolation for latency-sensitive services

Hello everyone My colleague and I uploaded a proposal to support CPU isolation for latency-sensitive services with cpuset, the issue is https://issues.apache.org/jira/browse/YARN-8320, detail design doc attached. If you are interested on this, we are looking forward for your comments and

[jira] [Created] (YARN-8345) NodeHealthCheckerService to differentiate between reason for UnusableNodes for client to act suitably on it

Kartik Bhatia created YARN-8345: --- Summary: NodeHealthCheckerService to differentiate between reason for UnusableNodes for client to act suitably on it Key: YARN-8345 URL:

[jira] [Resolved] (YARN-7998) RM crashes with NPE during recovering if ACL configuration was changed

[ https://issues.apache.org/jira/browse/YARN-7998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Shevchenko resolved YARN-7998. Resolution: Duplicate > RM crashes with NPE during recovering if ACL configuration

[jira] [Resolved] (YARN-7998) RM crashes with NPE during recovering if ACL configuration was changed

[ https://issues.apache.org/jira/browse/YARN-7998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Shevchenko resolved YARN-7998. Resolution: Fixed > RM crashes with NPE during recovering if ACL configuration was