Re: [DISCUSS] Set minimum version of Hadoop 3 to JDK8 (HADOOP-11858)

bq. We'll need to be strict after the switch: all patches to go into branch 2 will have to go through yetus as branch-2 patches, then cherry picked to trunk, or a separate patch on the same JIRA done for the branch-2. Assuming yetus still tests the branch-2 stuff on JDK7, that will check

[jira] [Resolved] (YARN-4955) Add retry for SocketTimeoutException in TimelineClient

[ https://issues.apache.org/jira/browse/YARN-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-4955. -- Resolution: Fixed > Add retry for SocketTimeoutException in TimelineCli

[jira] [Created] (YARN-4984) LogAggregationService shouldn't swallow exception in handling createAppDir() which cause thread leak.

Junping Du created YARN-4984: Summary: LogAggregationService shouldn't swallow exception in handling createAppDir() which cause thread leak. Key: YARN-4984 URL: https://issues.apache.org/jira/browse/YARN-4984

[jira] [Created] (YARN-4932) (Umbrella) YARN test failures on Windows

Junping Du created YARN-4932: Summary: (Umbrella) YARN test failures on Windows Key: YARN-4932 URL: https://issues.apache.org/jira/browse/YARN-4932 Project: Hadoop YARN Issue Type: Bug

Re: 2.7.3 release plan

Thanks for bringing up this topic, Sean. When I released our latest Hadoop release 2.6.4, the patch of HDFS-8791 haven't been committed in so that's why we didn't discuss this earlier. I remember in JIRA discussion, we treated this layout change as a Blocker bug that fixing a significant

[jira] [Created] (YARN-4893) Fix some intermittent test failures in TestRMAdminService2

Junping Du created YARN-4893: Summary: Fix some intermittent test failures in TestRMAdminService2 Key: YARN-4893 URL: https://issues.apache.org/jira/browse/YARN-4893 Project: Hadoop YARN Issue

[jira] [Created] (YARN-4863) AHS Security login should be in serviceInit() instead of serviceStart()

Junping Du created YARN-4863: Summary: AHS Security login should be in serviceInit() instead of serviceStart() Key: YARN-4863 URL: https://issues.apache.org/jira/browse/YARN-4863 Project: Hadoop YARN

[jira] [Created] (YARN-4832) NM side resource value should get updated if change applied in RM side

Junping Du created YARN-4832: Summary: NM side resource value should get updated if change applied in RM side Key: YARN-4832 URL: https://issues.apache.org/jira/browse/YARN-4832 Project: Hadoop YARN

[jira] [Created] (YARN-4791) Per user blacklist node for user specific error for container launch failure.

Junping Du created YARN-4791: Summary: Per user blacklist node for user specific error for container launch failure. Key: YARN-4791 URL: https://issues.apache.org/jira/browse/YARN-4791 Project: Hadoop

[jira] [Created] (YARN-4790) Per user blacklist node for user specific error for container launch failure.

Junping Du created YARN-4790: Summary: Per user blacklist node for user specific error for container launch failure. Key: YARN-4790 URL: https://issues.apache.org/jira/browse/YARN-4790 Project: Hadoop

Re: Question about YARN NodeManager and ApplicationMaster failures

With proper configuration, container (include AM) can still running when NM get failed. Please check YARN-1336 for NM restart work preserving. For AM failed (restart), after YARN-1489 (Work-preserving ApplicationMaster restart), the container will not get killed when AM failed (within maximum

Re: Looking to a Hadoop 3 release

Shall we consolidate effort for 2.8.0 and 3.0.0? It doesn't sounds reasonable to have two alpha releases to go in parallel. Is EC feature the main motivation of releasing hadoop 3 here? If so, I don't understand why this feature cannot land on 2.8.x or 2.9.x as an alpha feature. If we release

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

itical (and will be addressed in all future releases), and the concern Allen raised. Best, --Yongjun On Wed, Feb 10, 2016 at 8:37 AM, Allen Wittenauer <a...@altiscale.com> wrote: > > > On Feb 9, 2016, at 6:27 PM, Junping Du <j...@hortonworks.com> wrote: > > > > Thank

[RESULT] [VOTE] Release Apache Hadoop 2.6.4 RC0

this also can be ported to 2.6 > branch so it will help to specify labels at submission time. > > Thanks and Regards > Sunil > > On Wed, Feb 3, 2016 at 12:31 PM Junping Du <j...@hortonworks.com> wrote: > >> Hi community folks, >>I've created a release candida

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

hen we create new RCs. Thanks Akira for +1 on this proposed additional release step. Once we have an agreement on the details, we will update the wiki page accordingly. Best, --Yongjun On Tue, Feb 2, 2016 at 11:01 PM, Junping Du <j...@hortonworks.com> wrote: > Hi community folks, &g

Re: [DISCUSSION] Release Plan for Apache Hadoop 2.6.4

us now that 2.7.2 is done. In the mean while, I’ll get go dust off 2.8.0 too .. Thanks +Vinod > On Jan 6, 2016, at 3:59 PM, Junping Du <j...@hortonworks.com> wrote: > > Hello folks, > Hope everyone had a wonderful holiday and good rest in passed weeks. We > just ha

[jira] [Created] (YARN-4638) Node whitelist support for AM launching

Junping Du created YARN-4638: Summary: Node whitelist support for AM launching Key: YARN-4638 URL: https://issues.apache.org/jira/browse/YARN-4638 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-4636) Make blacklist tracking policy pluggable for more extensions.

Junping Du created YARN-4636: Summary: Make blacklist tracking policy pluggable for more extensions. Key: YARN-4636 URL: https://issues.apache.org/jira/browse/YARN-4636 Project: Hadoop YARN

[jira] [Created] (YARN-4635) Add global blacklist tracking for AM container failure.

Junping Du created YARN-4635: Summary: Add global blacklist tracking for AM container failure. Key: YARN-4635 URL: https://issues.apache.org/jira/browse/YARN-4635 Project: Hadoop YARN Issue Type

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

I give my binding +1 on 2.7.2-RC2 with following check: - All new commits (155) since 2.7.1 are included in commit log and CHANGES.txt which equally to JIRA marked as fixed in 2.7.2. - Signatures and message digests all are looks good, build get successfully from the source tar ball with JDK

[jira] [Created] (YARN-4600) More general services provided to application/container by YARN

Junping Du created YARN-4600: Summary: More general services provided to application/container by YARN Key: YARN-4600 URL: https://issues.apache.org/jira/browse/YARN-4600 Project: Hadoop YARN

[jira] [Created] (YARN-4601) HA as a general YARN service to highlighted container by application.

Junping Du created YARN-4601: Summary: HA as a general YARN service to highlighted container by application. Key: YARN-4601 URL: https://issues.apache.org/jira/browse/YARN-4601 Project: Hadoop YARN

[jira] [Created] (YARN-4602) Message/notification service between containers

Junping Du created YARN-4602: Summary: Message/notification service between containers Key: YARN-4602 URL: https://issues.apache.org/jira/browse/YARN-4602 Project: Hadoop YARN Issue Type: Sub

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

In addition, all new fixes backport from 2.6.3 doesn't listed in 2.7.2 entry of CHANGES.txt but keep listed as 2.6.3. I think this is fine no matter we have multiple entries to track the same commit or a single entry to track the earliest commit. The only thing matter is the commits in release

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

There are also several stale branches for YARN-2928 that we should consolidate: remotes/origin/YARN-2928 remotes/origin/YARN-2928-new remotes/origin/YARN-2928-old remotes/origin/YARN-2928-old-2015-11-09 remotes/origin/YARN-2928-rebase remotes/origin/feature-YARN-2928 (the latest one)

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

shape now.​ Thanks, Junping​ From: Vinod Kumar Vavilapalli <vino...@apache.org> Sent: Wednesday, January 13, 2016 11:15 PM To: Junping Du Cc: mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-...@hadoop.apache.org; hdfs-...@hadoop.apac

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

unds good to me. > > > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that > get out after 2.x.y release date" > > +1 > > > I would prefer this rule only applies on critical/blocker fixes, but not > applies on minor/trivial issues. >

[jira] [Created] (YARN-4576) Extend blacklist mechanism to protect AM failed multiple times on failure nodes

Junping Du created YARN-4576: Summary: Extend blacklist mechanism to protect AM failed multiple times on failure nodes Key: YARN-4576 URL: https://issues.apache.org/jira/browse/YARN-4576 Project: Hadoop

[jira] [Created] (YARN-4552) NM ResourceLocalizationService should check and initialize local filecache dir (and log dir) even if NM recover is enabled.

Junping Du created YARN-4552: Summary: NM ResourceLocalizationService should check and initialize local filecache dir (and log dir) even if NM recover is enabled. Key: YARN-4552 URL: https://issues.apache.org/jira

[DISCUSSION] Release Plan for Apache Hadoop 2.6.4

[1] Tickets fixed in 2.6.4: http://s.apache.org/vJB [2] Tickets targets for 2.6.4: http://s.apache.org/JpE From: Junping Du Sent: Thursday, December 17, 2015 1:36 PM To: common-...@hadoop.apache.org; yarn-dev@hadoop.apache.org Cc: hdfs-...@hadoop.apache

[jira] [Created] (YARN-4542) Cleanup AHS code and configuration

Junping Du created YARN-4542: Summary: Cleanup AHS code and configuration Key: YARN-4542 URL: https://issues.apache.org/jira/browse/YARN-4542 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-4527) Possible thread leak if TimelineClient.start() get called multiple times.

Junping Du created YARN-4527: Summary: Possible thread leak if TimelineClient.start() get called multiple times. Key: YARN-4527 URL: https://issues.apache.org/jira/browse/YARN-4527 Project: Hadoop YARN

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

rivial issues. Just 2 cents. Thanks, Junping From: Vinod Kumar Vavilapalli <vino...@apache.org> Sent: Thursday, December 24, 2015 12:47 AM To: Junping Du Cc: mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-...@hadoop.apache.org; hdfs-..

[jira] [Created] (YARN-4501) Document new put APIs in TimelineClient for ATS 1.5

Junping Du created YARN-4501: Summary: Document new put APIs in TimelineClient for ATS 1.5 Key: YARN-4501 URL: https://issues.apache.org/jira/browse/YARN-4501 Project: Hadoop YARN Issue Type

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

Checked 2.7.2-RC1 tag which match exactly with 2.7.2 branch. Downloaded the release bit and deploy a single node cluster which works fine with running some example jobs. Built from src and check signatures, all looks good. Checked release note which has 138 commits (HADOOP:22, HDFS:42,

Re: Highlighting communication on releases

Thanks Karthik to bring up the topic. Comparing with small enhancement on email distribution for release/branch news, I think a more important thing is to make our community (contributor & committer) to be more aware on ongoing releases/branches. I can see two improvements could be helpful

[RESULT] [VOTE] Release Apache Hadoop 2.6.3 RC0

shows expected usages > > > > On 12/11/15, 4:16 PM, "Junping Du" <j...@hortonworks.com> wrote: > >> >> Hi all developers in hadoop community, >> I've created a release candidate RC0 for Apache Hadoop 2.6.3 (the next >> maintenance release t

Re: [VOTE] Release Apache Hadoop 2.6.3 RC0

hdfs-...@hadoop.apache.org Subject: Re: [VOTE] Release Apache Hadoop 2.6.3 RC0 So, the original voting mail mentions we are voting on release-2.6.3-RC0 tag. Are we still doing that? What are the RC0.1 and RC1 tags doing then? +Vinod > On Dec 16, 2015, at 2:13 AM, Junping Du <j...@hortonwork

[jira] [Created] (YARN-4466) ResourceManager should tolerate unexpected exceptions to happen in non-critical subsystem/services like SystemMetricsPublisher

Junping Du created YARN-4466: Summary: ResourceManager should tolerate unexpected exceptions to happen in non-critical subsystem/services like SystemMetricsPublisher Key: YARN-4466 URL: https://issues.apache.org/jira

Re: [VOTE] Release Apache Hadoop 2.6.3 RC0

single node cluster setup and verified few MR jobs), >>>> submission of Unmanaged AM is getting the RM down. YARN-4452 has >>>> already been raised and i am working on it. Will provide the patch for >>>> the trunk and the 2.6.3 version asap >>>> >>>> Regards, >&

Re: [VOTE] Release Apache Hadoop 2.6.3 RC0

permission error. Could you check the permission to access the files? > Forbidden > You don't have permission to access > /~junping_du/hadoop-2.6.3-RC0/hadoop-2.6.3-RC0-src.tar.gz on this server. Thanks, - Tsuyoshi On Sat, Dec 12, 2015 at 9:16 AM, Junping Du <j...@hortonworks.com<

[VOTE] Release Apache Hadoop 2.6.3 RC0

Hi all developers in hadoop community, I've created a release candidate RC0 for Apache Hadoop 2.6.3 (the next maintenance release to follow up 2.6.2.) according to email thread of release plan 2.6.3 [1]. Sorry for this RC coming a bit late as several blocker issues were getting committed

Fw: ApacheCon NA 2015 Travel Assistance Applications now open!

FYI. Thanks, From: lewis john mcgibbney Sent: Tuesday, December 08, 2015 4:15 AM Cc: travel-assista...@apache.org Subject: ApacheCon NA 2015 Travel Assistance Applications now open! Hi pmcs@, The Travel Assistance Committee (TAC)

[jira] [Created] (YARN-4429) RetryPolicies (other than FailoverOnNetworkExceptionRetry) should put on retry failed reason or the log from RMProxy's retry could be very misleading.

Junping Du created YARN-4429: Summary: RetryPolicies (other than FailoverOnNetworkExceptionRetry) should put on retry failed reason or the log from RMProxy's retry could be very misleading. Key: YARN-4429 URL: https

[jira] [Created] (YARN-4431) Not necessary to do unRegisterNM() if NM get stop due to failed to connect to RM

Junping Du created YARN-4431: Summary: Not necessary to do unRegisterNM() if NM get stop due to failed to connect to RM Key: YARN-4431 URL: https://issues.apache.org/jira/browse/YARN-4431 Project: Hadoop

Release plan for Apache Hadoop 2.6.3

forward open tickets [2].​ Thanks, Junping [1] 2.6.3 Fixed Tickets: http://s.apache.org/Ylq [2] 2.6.3 Tickets: http://s.apache.org/9A7 From: Junping Du Sent: Tuesday, December 01, 2015 12:26 PM To: Vinod Kumar Vavilapalli Cc: Sangjin Lee; mapreduce

[jira] [Created] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

Junping Du created YARN-4403: Summary: (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period Key: YARN-4403 URL: https://issues.apache.org/jira/browse/YARN-4403 Project

Re: continuing releases on Apache Hadoop 2.6.x

xu via jlowe) 7K Thanks, Junping From: Vinod Kumar Vavilapalli <vino...@apache.org> Sent: Monday, November 30, 2015 9:23 PM To: Junping Du Cc: Sangjin Lee; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Hadoop Common; hdfs-...@hadoop.a

Re: continuing releases on Apache Hadoop 2.6.x

org> Sent: Wednesday, November 25, 2015 6:55 PM To: Junping Du Cc: mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Hadoop Common; hdfs-...@hadoop.apache.org; Vinod Vavilapalli; Haohui Mai; Chris Trezzo Subject: Re: continuing releases on Apache Hadoop 2.6.x If the speed and clarity a

Re: continuing releases on Apache Hadoop 2.6.x

lready have in would > like to see their work out there. > > On Fri, Nov 20, 2015 at 7:51 AM, Junping Du <j...@hortonworks.com> wrote: > > > +1. Early Dec sounds too early for 2.6.3 release given we only have 18 > > patches since recently release 2.6.2. > >

[jira] [Created] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

Junping Du created YARN-4389: Summary: "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster Key: YARN-4389

[jira] [Created] (YARN-4388) Cleanup "mapreduce.job.hdfs-servers" from yarn-default.xml

Junping Du created YARN-4388: Summary: Cleanup "mapreduce.job.hdfs-servers" from yarn-default.xml Key: YARN-4388 URL: https://issues.apache.org/jira/browse/YARN-4388 Project: Hadoop YARN

Re: continuing releases on Apache Hadoop 2.6.x

+1. Early Dec sounds too early for 2.6.3 release given we only have 18 patches since recently release 2.6.2. We should nominate more fixes and wait a while for the feedback on 2.6.2. Thanks, Junping From: Vinod Vavilapalli Sent:

Re: continuing releases on Apache Hadoop 2.6.x

Thanks Chris Trezzo for volunteer on helping 2.6.3 release. I think Sangjin was asking for a committer to serve as release manager for 2.6.3 according to Apache rules: http://www.apache.org/dev/release-publishing.html. I would like to serve as that role to work closely with you and Sangjin on

[jira] [Created] (YARN-4351) Tests in h.y.c.TestGetGroups get failed on trunk

Junping Du created YARN-4351: Summary: Tests in h.y.c.TestGetGroups get failed on trunk Key: YARN-4351 URL: https://issues.apache.org/jira/browse/YARN-4351 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-4352) Timeout for tests in TestYarnClient, TestAMRMClient and TestNMClient

Junping Du created YARN-4352: Summary: Timeout for tests in TestYarnClient, TestAMRMClient and TestNMClient Key: YARN-4352 URL: https://issues.apache.org/jira/browse/YARN-4352 Project: Hadoop YARN

[jira] [Resolved] (YARN-1949) Add admin ACL check to AdminService#updateNodeResource()

[ https://issues.apache.org/jira/browse/YARN-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-1949. -- Resolution: Duplicate The core change for ACL update is already included in YARN-1506, so I close

[jira] [Created] (YARN-4346) Test committer.commitJob() behavior during committing when MR AM get failed.

Junping Du created YARN-4346: Summary: Test committer.commitJob() behavior during committing when MR AM get failed. Key: YARN-4346 URL: https://issues.apache.org/jira/browse/YARN-4346 Project: Hadoop

[jira] [Created] (YARN-4288) NodeManager restart should keep retrying to register to RM while connection exception happens during RM restart

Junping Du created YARN-4288: Summary: NodeManager restart should keep retrying to register to RM while connection exception happens during RM restart Key: YARN-4288 URL: https://issues.apache.org/jira/browse/YARN

[jira] [Created] (YARN-4274) NodeStatusUpdaterImpl should register to RM again after a non-fatal exception happen before

Junping Du created YARN-4274: Summary: NodeStatusUpdaterImpl should register to RM again after a non-fatal exception happen before Key: YARN-4274 URL: https://issues.apache.org/jira/browse/YARN-4274

Re: [YARN-2928] rebasing to trunk

Thanks for the work, Sangjin! Please go ahead to complete rebase. About moving TestRPC from hadoop-common to hadoop-server-common, we were adding "testRPCOnCollectorNodeManagerProtocol" by reusing existing code in TestRPC which deal with server protocol so have to stay in hadoop-server-common

Re: [VOTE] Merge YARN-1197 container resize into trunk

+1. (Binding). Thanks, Junping From: Wangda Tan Sent: Thursday, September 17, 2015 3:19 AM To: yarn-dev@hadoop.apache.org Subject: Re: [VOTE] Merge YARN-1197 container resize into trunk +1 (non-binding), Thanks Jian starting this

Re: [VOTE] Release Apache Hadoop 2.6.1 RC1

+1 (binding) with: - Download and verify signatures. - Build and deploy a single node cluster. - Run some example jobs (PI, etc.) on deployed cluster. Thanks, Junping From: Rohith Sharma K S Sent: Monday, September 21, 2015

[jira] [Created] (YARN-4160) Dynamic NM Resources Configuration file should be simplified.

Junping Du created YARN-4160: Summary: Dynamic NM Resources Configuration file should be simplified. Key: YARN-4160 URL: https://issues.apache.org/jira/browse/YARN-4160 Project: Hadoop YARN

Re: YARN-2928 branch reset

be fixed separately? Thanks, Junping From: Naganarasimha G R (Naga) garlanaganarasi...@huawei.com Sent: Friday, August 14, 2015 3:59 PM To: Li Lu; Vinod Kumar Vavilapalli Cc: yarn-dev@hadoop.apache.org; Zhijie Shen; Junping Du; Sangjin Lee; Vrushali

[jira] [Created] (YARN-4031) Add JvmPauseMonitor to ApplicationHistoryServer

Junping Du created YARN-4031: Summary: Add JvmPauseMonitor to ApplicationHistoryServer Key: YARN-4031 URL: https://issues.apache.org/jira/browse/YARN-4031 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-3959) Store application related configurations in Timeline Service v2

Junping Du created YARN-3959: Summary: Store application related configurations in Timeline Service v2 Key: YARN-3959 URL: https://issues.apache.org/jira/browse/YARN-3959 Project: Hadoop YARN

[jira] [Created] (YARN-3815) [Aggregation] Application/Flow/User/Queue Level Aggregations

Junping Du created YARN-3815: Summary: [Aggregation] Application/Flow/User/Queue Level Aggregations Key: YARN-3815 URL: https://issues.apache.org/jira/browse/YARN-3815 Project: Hadoop YARN

[jira] [Created] (YARN-3817) Flow and User level aggregation on Application States table

Junping Du created YARN-3817: Summary: Flow and User level aggregation on Application States table Key: YARN-3817 URL: https://issues.apache.org/jira/browse/YARN-3817 Project: Hadoop YARN Issue

[jira] [Created] (YARN-3695) EOFException shouldn't be retry forever in RMProxy

Junping Du created YARN-3695: Summary: EOFException shouldn't be retry forever in RMProxy Key: YARN-3695 URL: https://issues.apache.org/jira/browse/YARN-3695 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-3641) stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

Junping Du created YARN-3641: Summary: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services. Key: YARN-3641 URL: https://issues.apache.org/jira/browse/YARN-3641

[jira] [Resolved] (YARN-3599) Fix the javadoc of DelegationTokenSecretManager in hadoop-yarn

[ https://issues.apache.org/jira/browse/YARN-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-3599. -- Resolution: Duplicate Fix the javadoc of DelegationTokenSecretManager in hadoop-yarn

[jira] [Resolved] (YARN-3596) Fix the javadoc of DelegationTokenSecretManager in hadoop-common

[ https://issues.apache.org/jira/browse/YARN-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-3596. -- Resolution: Duplicate Fix the javadoc of DelegationTokenSecretManager in hadoop-common

[jira] [Resolved] (YARN-3597) Fix the javadoc of DelegationTokenSecretManager in hadoop-hdfs

[ https://issues.apache.org/jira/browse/YARN-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-3597. -- Resolution: Duplicate Fix the javadoc of DelegationTokenSecretManager in hadoop-hdfs

[jira] [Resolved] (YARN-3598) Fix the javadoc of DelegationTokenSecretManager in hadoop-mapreduce

[ https://issues.apache.org/jira/browse/YARN-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-3598. -- Resolution: Duplicate Fix the javadoc of DelegationTokenSecretManager in hadoop-mapreduce

[jira] [Created] (YARN-3592) Fix typos in RMNodeLabelsManager

Junping Du created YARN-3592: Summary: Fix typos in RMNodeLabelsManager Key: YARN-3592 URL: https://issues.apache.org/jira/browse/YARN-3592 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-3586) RM only get back addresses of Collectors that NM needs to know.

Junping Du created YARN-3586: Summary: RM only get back addresses of Collectors that NM needs to know. Key: YARN-3586 URL: https://issues.apache.org/jira/browse/YARN-3586 Project: Hadoop YARN

[jira] [Resolved] (YARN-2470) A high value for yarn.nodemanager.delete.debug-delay-sec causes Nodemanager to crash. Slider needs this value to be high. Setting a very high value throws an exception an

[ https://issues.apache.org/jira/browse/YARN-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2470. -- Resolution: Won't Fix A high value for yarn.nodemanager.delete.debug-delay-sec causes Nodemanager

[jira] [Resolved] (YARN-2483) TestAMRestart#testShouldNotCountFailureToMaxAttemptRetry fails due to incorrect AppAttempt state

[ https://issues.apache.org/jira/browse/YARN-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2483. -- Resolution: Duplicate Target Version/s: (was: 2.6.0) Resolve this JIRA as duplicated

[jira] [Resolved] (YARN-2445) ATS does not reflect changes to uploaded TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2445. -- Resolution: Won't Fix Agree with [~billie.rinaldi]'s comments above, this is expected behavior. ATS

[jira] [Resolved] (YARN-670) Add an Exception to indicate 'Maintenance' for NMs and add this to the JavaDoc for appropriate protocols

[ https://issues.apache.org/jira/browse/YARN-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-670. - Resolution: Won't Fix Add an Exception to indicate 'Maintenance' for NMs and add this to the JavaDoc

[jira] [Resolved] (YARN-964) Give a parameter that can set AM retry interval

[ https://issues.apache.org/jira/browse/YARN-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-964. - Resolution: Won't Fix Agree with [~vinodkv]. Resolve this as won't fix. Give a parameter that can set AM

[jira] [Resolved] (YARN-2365) TestAMRestart.testShouldNotCountFailureToMaxAttemptRetry fails on branch-2

[ https://issues.apache.org/jira/browse/YARN-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2365. -- Resolution: Cannot Reproduce TestAMRestart.testShouldNotCountFailureToMaxAttemptRetry fails on branch-2

[jira] [Created] (YARN-3567) Document exit codes and their meanings used by LinuxContainerExecutor.

Junping Du created YARN-3567: Summary: Document exit codes and their meanings used by LinuxContainerExecutor. Key: YARN-3567 URL: https://issues.apache.org/jira/browse/YARN-3567 Project: Hadoop YARN

[jira] [Resolved] (YARN-2334) Document exit codes and their meanings used by linux task controller.

[ https://issues.apache.org/jira/browse/YARN-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2334. -- Resolution: Not A Problem Document exit codes and their meanings used by linux task controller

[jira] [Resolved] (YARN-2364) TestRMRestart#testRMRestartWaitForPreviousAMToFinish is racy

[ https://issues.apache.org/jira/browse/YARN-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2364. -- Resolution: Duplicate Duplicated with YARN-1468 TestRMRestart#testRMRestartWaitForPreviousAMToFinish

[jira] [Resolved] (YARN-2390) Investigating whether generic history service needs to support queue-acls

[ https://issues.apache.org/jira/browse/YARN-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2390. -- Resolution: Won't Fix Investigating whether generic history service needs to support queue-acls

[jira] [Resolved] (YARN-2401) Rethinking of the HTTP method of TimelineWebServices#postEntities

[ https://issues.apache.org/jira/browse/YARN-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2401. -- Resolution: Won't Fix Rethinking of the HTTP method of TimelineWebServices#postEntities

[jira] [Resolved] (YARN-2398) TestResourceTrackerOnHA crashes

[ https://issues.apache.org/jira/browse/YARN-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2398. -- Resolution: Cannot Reproduce TestResourceTrackerOnHA crashes

[jira] [Resolved] (YARN-880) Configuring map/reduce memory equal to nodemanager's memory, hangs the job execution

[ https://issues.apache.org/jira/browse/YARN-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-880. - Resolution: Not A Problem Assignee: (was: Omkar Vinit Joshi) Configuring map/reduce memory equal

[jira] [Resolved] (YARN-943) RM starts 2 attempts of failed app even though am-max-retries is set to 1

[ https://issues.apache.org/jira/browse/YARN-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-943. - Resolution: Not A Problem Assignee: (was: Zhijie Shen) RM starts 2 attempts of failed app even

[jira] [Resolved] (YARN-3431) Sub resources of timeline entity needs to be passed to a separate endpoint.

[ https://issues.apache.org/jira/browse/YARN-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-3431. -- Resolution: Fixed Fix Version/s: YARN-2928 Hadoop Flags: Reviewed I have commit this to YARN

[jira] [Created] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

Junping Du created YARN-3505: Summary: Node's Log Aggregation Report with SUCCEED should not cached in RMApps Key: YARN-3505 URL: https://issues.apache.org/jira/browse/YARN-3505 Project: Hadoop YARN

[jira] [Created] (YARN-3488) AM get timeline service info from RM rather than Application specific configuration.

Junping Du created YARN-3488: Summary: AM get timeline service info from RM rather than Application specific configuration. Key: YARN-3488 URL: https://issues.apache.org/jira/browse/YARN-3488 Project

Re: [VOTE] Release Apache Hadoop 2.7.0 RC0

+1. (Non-binding) - Download and verify the checksum on src and binary locally. - Deploy a single node cluster and play with simple MR jobs, i.e. PI, Terasort, etc. All looks fine for now. Thanks, Junping From: Vinod Kumar Vavilapalli vino...@apache.org

Re: A 2.7.1 release to follow up 2.7.0

+1 (non-binding). The plan sounds reasonable. We should make our release train more fast-moving, and predictable - it could benefit our community and ecosystem in many aspects. Thanks, Junping From: Arpit Agarwal aagar...@hortonworks.com Sent: Thursday,

[jira] [Resolved] (YARN-3449) Recover appTokenKeepAliveMap upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-3449. -- Resolution: Invalid Assignee: (was: Junping Du) Recover appTokenKeepAliveMap upon nodemanager

[jira] [Resolved] (YARN-329) yarn CHANGES.txt link missing from docs Reference

[ https://issues.apache.org/jira/browse/YARN-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-329. - Resolution: Fixed Fix Version/s: 2.6.0 This get fixed since 2.6.0 release. Mark it as resolved

[jira] [Resolved] (YARN-374) Job History Server doesn't show jobs which killed by ClientRMProtocol.forceKillApplication

[ https://issues.apache.org/jira/browse/YARN-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-374. - Resolution: Not a Problem Job History Server doesn't show jobs which killed

[jira] [Resolved] (YARN-2969) allocate resource on different nodes for task

[ https://issues.apache.org/jira/browse/YARN-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2969. -- Resolution: Duplicate allocate resource on different nodes for task

<    1   2   3   >