[jira] [Updated] (YARN-3753) RM failed to come up with "java.io.IOException: Wait for ZKClient creation timed out"

[ https://issues.apache.org/jira/browse/YARN-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3753: -- Attachment: YARN-3753.2.patch > RM failed to come up with "java.io.IOException: Wait for ZKClient creation > tim

[jira] [Commented] (YARN-3764) CapacityScheduler should forbid moving LeafQueue from one parent to another

[ https://issues.apache.org/jira/browse/YARN-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571872#comment-14571872 ] Jian He commented on YARN-3764: --- looks good, +1 > CapacityScheduler should forbid moving Lea

[jira] [Commented] (YARN-2392) add more diags about app retry limits on AM failures

[ https://issues.apache.org/jira/browse/YARN-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573293#comment-14573293 ] Jian He commented on YARN-2392: --- looks good, committing > add more diags about app retry lim

[jira] [Commented] (YARN-2716) Refactor ZKRMStateStore retry code with Apache Curator

[ https://issues.apache.org/jira/browse/YARN-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573911#comment-14573911 ] Jian He commented on YARN-2716: --- Thanks Karthik for working this ! This simplifies things a l

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574935#comment-14574935 ] Jian He commented on YARN-3508: --- I think this make sense to move preemption events from main

[jira] [Commented] (YARN-2716) Refactor ZKRMStateStore retry code with Apache Curator

[ https://issues.apache.org/jira/browse/YARN-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575395#comment-14575395 ] Jian He commented on YARN-2716: --- bq. safeDelete checks if the znode exists before attempting

[jira] [Commented] (YARN-2716) Refactor ZKRMStateStore retry code with Apache Curator

[ https://issues.apache.org/jira/browse/YARN-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575417#comment-14575417 ] Jian He commented on YARN-2716: --- bq. creates and deletes the fencing node as well. I see, tha

[jira] [Commented] (YARN-2716) Refactor ZKRMStateStore retry code with Apache Curator

[ https://issues.apache.org/jira/browse/YARN-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577899#comment-14577899 ] Jian He commented on YARN-2716: --- looks good , committing > Refactor ZKRMStateStore retry cod

[jira] [Commented] (YARN-3017) ContainerID in ResourceManager Log Has Slightly Different Format From AppAttemptID

[ https://issues.apache.org/jira/browse/YARN-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583854#comment-14583854 ] Jian He commented on YARN-3017: --- IMHO, although this theoretically doesn't break compatibilit

[jira] [Commented] (YARN-3804) Both RM are on standBy state when kerberos user not in yarn.admin.acl

[ https://issues.apache.org/jira/browse/YARN-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586610#comment-14586610 ] Jian He commented on YARN-3804: --- +1 for 2) Not too much point having RM to depend on the admi

[jira] [Commented] (YARN-3811) NM restarts could lead to app failures

[ https://issues.apache.org/jira/browse/YARN-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589256#comment-14589256 ] Jian He commented on YARN-3811: --- I'm actually thinking do we still need the NMNotYetReadyExce

[jira] [Commented] (YARN-3811) NM restarts could lead to app failures

[ https://issues.apache.org/jira/browse/YARN-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590319#comment-14590319 ] Jian He commented on YARN-3811: --- bq. this is not possible to do as the NM needs to report the

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593676#comment-14593676 ] Jian He commented on YARN-3798: --- [~rakeshr], thanks for coming to this. I have one question,

[jira] [Commented] (YARN-3790) TestWorkPreservingRMRestart#testSchedulerRecovery fails intermittently in trunk for FS scheduler

[ https://issues.apache.org/jira/browse/YARN-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596441#comment-14596441 ] Jian He commented on YARN-3790: --- lgtm, thanks [~zxu] and [~rohithsharma] > TestWorkPreservin

[jira] [Commented] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596481#comment-14596481 ] Jian He commented on YARN-1963: --- I think we need to move this forward.. Overall, I prefer us

[jira] [Commented] (YARN-3842) NM restarts could lead to app failures

[ https://issues.apache.org/jira/browse/YARN-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596776#comment-14596776 ] Jian He commented on YARN-3842: --- I think the latest patch is safe for 2.7.1, +1 > NM restar

[jira] [Created] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

Jian He created YARN-3855: - Summary: If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup Key: YARN-3855 URL: https://issues.apache.org/jira/browse/YARN-3855

[jira] [Commented] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602040#comment-14602040 ] Jian He commented on YARN-3855: --- Today, RMAuthenticationFilterInitializer is always added in

[jira] [Updated] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3855: -- Description: If all ACLs (admin acl, queue-admin-acls etc.) are setup properly and "http.authentication.type" is

[jira] [Updated] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3855: -- Description: If all ACLs (admin acl, queue-admin-acls etc.) are setup properly and "http.authentication.type" is

[jira] [Updated] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3855: -- Attachment: YARN-3855.1.patch Uploaded a patch to always add the RMAuthenticationFilterInitializer/Authenticatio

[jira] [Commented] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602295#comment-14602295 ] Jian He commented on YARN-3855: --- bq. This is a misconfiguration, plain and simple. we do see

[jira] [Comment Edited] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602295#comment-14602295 ] Jian He edited comment on YARN-3855 at 6/26/15 2:38 AM: bq. This is

[jira] [Commented] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602341#comment-14602341 ] Jian He commented on YARN-3855: --- I believe what you suggested is a general good practice to s

[jira] [Updated] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3855: -- Attachment: YARN-3855.2.patch > If acl is enabled and http.authentication.type is simple, user cannot view > the

[jira] [Comment Edited] (YARN-3855) If acl is enabled and http.authentication.type is simple, user cannot view the app page in default setup

[ https://issues.apache.org/jira/browse/YARN-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602341#comment-14602341 ] Jian He edited comment on YARN-3855 at 6/26/15 4:35 AM: I believe w

[jira] [Commented] (YARN-3695) ServerProxy (NMProxy, etc.) shouldn't retry forever for non network exception.

[ https://issues.apache.org/jira/browse/YARN-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603710#comment-14603710 ] Jian He commented on YARN-3695: --- looks good, +1 > ServerProxy (NMProxy, etc.) shouldn't retr

[jira] [Commented] (YARN-5098) Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation token

[ https://issues.apache.org/jira/browse/YARN-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308513#comment-15308513 ] Jian He commented on YARN-5098: --- TestClientToAMTokens is tracked by YARN-5163 The other test

[jira] [Updated] (YARN-5098) Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation token

[ https://issues.apache.org/jira/browse/YARN-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5098: -- Attachment: YARN-5098.2.patch Fix the check style warnings. Left the ones that are invalid. > Yarn Application

[jira] [Commented] (YARN-1815) Work preserving recovery of Unmanged AMs

[ https://issues.apache.org/jira/browse/YARN-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312813#comment-15312813 ] Jian He commented on YARN-1815: --- Thanks Subru ! looks good overall, few comments on the patch

[jira] [Commented] (YARN-5190) Registering/unregistering container metrics triggered by ContainerEvent and ContainersMonitorEvent are conflict which cause uncaught exception in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312850#comment-15312850 ] Jian He commented on YARN-5190: --- looks good, only minor comments on the format: is below slig

[jira] [Updated] (YARN-5098) Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation token

[ https://issues.apache.org/jira/browse/YARN-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5098: -- Attachment: YARN-5098.3.patch fixed the long lines. the warning about whitespace is invalid. that line does not

[jira] [Commented] (YARN-5098) Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation token

[ https://issues.apache.org/jira/browse/YARN-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314483#comment-15314483 ] Jian He commented on YARN-5098: --- the last checkstyle warning is invalid > Yarn Application

[jira] [Commented] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315054#comment-15315054 ] Jian He commented on YARN-4757: --- Hi [~jmaron], thanks for working on this. I went through t

[jira] [Comment Edited] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315054#comment-15315054 ] Jian He edited comment on YARN-4757 at 6/3/16 10:59 PM: Hi [~jmaron

[jira] [Commented] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317309#comment-15317309 ] Jian He commented on YARN-4757: --- [~jmaron], thanks for your reply ! few other questions: bq.

[jira] [Commented] (YARN-1942) Many of ConverterUtils methods need to have public interfaces

[ https://issues.apache.org/jira/browse/YARN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319851#comment-15319851 ] Jian He commented on YARN-1942: --- patch looks good, are the test failures related ? > Many of

[jira] [Commented] (YARN-5218) Submit initial DNS server approach for review

[ https://issues.apache.org/jira/browse/YARN-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322948#comment-15322948 ] Jian He commented on YARN-5218: --- This patch is moved from YARN-4757. This is the core change

[jira] [Updated] (YARN-5083) YARN CLI for AM logs does not give any error message if entered invalid am value

[ https://issues.apache.org/jira/browse/YARN-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5083: -- Attachment: YARN-5083.1.patch > YARN CLI for AM logs does not give any error message if entered invalid am > val

[jira] [Assigned] (YARN-5083) YARN CLI for AM logs does not give any error message if entered invalid am value

[ https://issues.apache.org/jira/browse/YARN-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-5083: - Assignee: Jian He (was: Xuan Gong) > YARN CLI for AM logs does not give any error message if entered inva

[jira] [Commented] (YARN-5083) YARN CLI for AM logs does not give any error message if entered invalid am value

[ https://issues.apache.org/jira/browse/YARN-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323062#comment-15323062 ] Jian He commented on YARN-5083: --- Simple patch to add the error message. > YARN CLI for AM lo

[jira] [Updated] (YARN-5083) YARN CLI for AM logs does not give any error message if entered invalid am value

[ https://issues.apache.org/jira/browse/YARN-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5083: -- Attachment: YARN-5083.1.patch > YARN CLI for AM logs does not give any error message if entered invalid am > val

[jira] [Assigned] (YARN-5122) "yarn logs" for running containers should print an explicit footer saying that the log may be incomplete

[ https://issues.apache.org/jira/browse/YARN-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-5122: - Assignee: Jian He (was: Vinod Kumar Vavilapalli) > "yarn logs" for running containers should print an exp

[jira] [Updated] (YARN-5122) "yarn logs" for running containers should print an explicit footer saying that the log may be incomplete

[ https://issues.apache.org/jira/browse/YARN-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5122: -- Attachment: YARN-5122.1.patch add the message in the end of the running container log when running yarn logs com

[jira] [Created] (YARN-5227) yarn logs command: no need to specify -applicaionId when specifying containerId

Jian He created YARN-5227: - Summary: yarn logs command: no need to specify -applicaionId when specifying containerId Key: YARN-5227 URL: https://issues.apache.org/jira/browse/YARN-5227 Project: Hadoop YARN

[jira] [Updated] (YARN-5122) "yarn logs" for running containers should print an explicit footer saying that the log may be incomplete

[ https://issues.apache.org/jira/browse/YARN-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5122: -- Attachment: YARN-5122.1.patch > "yarn logs" for running containers should print an explicit footer saying > that

[jira] [Commented] (YARN-1942) Many of ConverterUtils methods need to have public interfaces

[ https://issues.apache.org/jira/browse/YARN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323413#comment-15323413 ] Jian He commented on YARN-1942: --- lgtm, thanks > Many of ConverterUtils methods need to have

[jira] [Commented] (YARN-1942) Many of ConverterUtils methods need to have public interfaces

[ https://issues.apache.org/jira/browse/YARN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323922#comment-15323922 ] Jian He commented on YARN-1942: --- [~leftnoteasy], patch does not apply to branch-2, could you

[jira] [Updated] (YARN-5122) "yarn logs" for running containers should print an explicit footer saying that the log may be incomplete

[ https://issues.apache.org/jira/browse/YARN-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5122: -- Attachment: YARN-5122.2.patch > "yarn logs" for running containers should print an explicit footer saying > that

[jira] [Commented] (YARN-5122) "yarn logs" for running containers should print an explicit footer saying that the log may be incomplete

[ https://issues.apache.org/jira/browse/YARN-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325593#comment-15325593 ] Jian He commented on YARN-5122: --- no specific reason, reverted that change any way. submit a

[jira] [Commented] (YARN-5083) YARN CLI for AM logs does not give any error message if entered invalid am value

[ https://issues.apache.org/jira/browse/YARN-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325605#comment-15325605 ] Jian He commented on YARN-5083: --- The highlighted one in blue is the right one. I'll change t

[jira] [Updated] (YARN-5122) "yarn logs" for running containers should print an explicit footer saying that the log may be incomplete

[ https://issues.apache.org/jira/browse/YARN-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5122: -- Attachment: YARN-5122.3.patch > "yarn logs" for running containers should print an explicit footer saying > that

[jira] [Updated] (YARN-5218) Initial core change for DNS for YARN.

[ https://issues.apache.org/jira/browse/YARN-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5218: -- Summary: Initial core change for DNS for YARN. (was: Submit initial DNS server approach for review) > Initial c

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326587#comment-15326587 ] Jian He commented on YARN-5124: --- branch-2 compilation broke because of this. [~asuresh], can

[jira] [Commented] (YARN-5122) "yarn logs" for running containers should print an explicit footer saying that the log may be incomplete

[ https://issues.apache.org/jira/browse/YARN-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327845#comment-15327845 ] Jian He commented on YARN-5122: --- It's not straightforward to add a unit test. I've tested loc

[jira] [Commented] (YARN-1942) Many of ConverterUtils methods need to have public interfaces

[ https://issues.apache.org/jira/browse/YARN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330711#comment-15330711 ] Jian He commented on YARN-1942: --- lgtm, thanks ! > Many of ConverterUtils methods need to hav

[jira] [Updated] (YARN-5083) YARN CLI for AM logs does not give any error message if entered invalid am value

[ https://issues.apache.org/jira/browse/YARN-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5083: -- Attachment: YARN-5083.2.patch new patch addressed the comment > YARN CLI for AM logs does not give any error mes

[jira] [Commented] (YARN-5292) Support for PAUSED container state

[ https://issues.apache.org/jira/browse/YARN-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348641#comment-15348641 ] Jian He commented on YARN-5292: --- For the case mentioned in description, if a container is fre

[jira] [Created] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

Jian He created YARN-5294: - Summary: Pass remote ip address down to YarnAuthorizationProvider Key: YARN-5294 URL: https://issues.apache.org/jira/browse/YARN-5294 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294.1.patch > Pass remote ip address down to YarnAuthorizationProvider > --

[jira] [Commented] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

[ https://issues.apache.org/jira/browse/YARN-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348860#comment-15348860 ] Jian He commented on YARN-5227: --- thanks for working on this. The error message seems contrad

[jira] [Commented] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

[ https://issues.apache.org/jira/browse/YARN-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348949#comment-15348949 ] Jian He commented on YARN-5227: --- oh, I misread. I interpreted as "If containerId is specifie

[jira] [Commented] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

[ https://issues.apache.org/jira/browse/YARN-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351816#comment-15351816 ] Jian He commented on YARN-5227: --- i see, thanks for the explanation ! > yarn logs command: no

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351854#comment-15351854 ] Jian He commented on YARN-5270: --- QueueMetrics - the getters for availableVCores, pendingVCore

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351859#comment-15351859 ] Jian He commented on YARN-5296: --- lgtm > NMs going OutOfMemory because ContainerMetrics leak

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294.2.patch > Pass remote ip address down to YarnAuthorizationProvider > --

[jira] [Commented] (YARN-5262) Optimize sending RMNodeFinishedContainersPulledByAMEvent for every AM heartbeat

[ https://issues.apache.org/jira/browse/YARN-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351995#comment-15351995 ] Jian He commented on YARN-5262: --- lgtm, good findings ! > Optimize sending RMNodeFinishedCon

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294.3.patch > Pass remote ip address down to YarnAuthorizationProvider > --

[jira] [Commented] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352026#comment-15352026 ] Jian He commented on YARN-5294: --- Uploaded a patch which pass in the remote address and forwar

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359620#comment-15359620 ] Jian He commented on YARN-5296: --- I analyzed the memory heap dump together with Junping. This

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359636#comment-15359636 ] Jian He commented on YARN-5296: --- yep, we'll run more testing to verify if the oom is resolved

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359674#comment-15359674 ] Jian He commented on YARN-5296: --- No, this does not need to be in 2.7.3 > NMs going OutOfMemo

[jira] [Commented] (YARN-5302) Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation token II

[ https://issues.apache.org/jira/browse/YARN-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363156#comment-15363156 ] Jian He commented on YARN-5302: --- Hi [~xinxianyin], [~Naganarasimha] I think if NM restarts, i

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294.4.patch > Pass remote ip address down to YarnAuthorizationProvider > --

[jira] [Commented] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363205#comment-15363205 ] Jian He commented on YARN-5294: --- The AccessRequest.java is added in 2.9, I think it should be

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363216#comment-15363216 ] Jian He commented on YARN-5296: --- lgtm, thanks for catching this ! > NMs going OutOfMemory be

[jira] [Commented] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

[ https://issues.apache.org/jira/browse/YARN-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363261#comment-15363261 ] Jian He commented on YARN-5227: --- [~GergelyNovak], is the unit failure related to this patch ?

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294.5.patch fixed the javac warning > Pass remote ip address down to YarnAuthorizationProvider

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294.6.patch > Pass remote ip address down to YarnAuthorizationProvider > --

[jira] [Commented] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363783#comment-15363783 ] Jian He commented on YARN-5294: --- minor comment: this logic could be simplified to throw excep

[jira] [Issue Comment Deleted] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Comment: was deleted (was: minor comment: this logic could be simplified to throw exception directly. {code}

[jira] [Commented] (YARN-5233) Support for specifying a path for ATS plugin jars

[ https://issues.apache.org/jira/browse/YARN-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364676#comment-15364676 ] Jian He commented on YARN-5233: --- minor comment: this logic could be simplified to throw excep

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294-branch-2.patch upload branch-2 patch > Pass remote ip address down to YarnAuthorizationPro

[jira] [Commented] (YARN-5233) Support for specifying a path for ATS plugin jars

[ https://issues.apache.org/jira/browse/YARN-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365202#comment-15365202 ] Jian He commented on YARN-5233: --- lgtm > Support for specifying a path for ATS plugin jars >

[jira] [Updated] (YARN-5233) Support for specifying a path for ATS plugin jars

[ https://issues.apache.org/jira/browse/YARN-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5233: -- Affects Version/s: (was: 2.8.0) 2.9.0 Target Version/s: 2.9.0 Committed to trunk

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366807#comment-15366807 ] Jian He commented on YARN-5270: --- - should the proto definition be reverted to int32 too ? {co

[jira] [Comment Edited] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366807#comment-15366807 ] Jian He edited comment on YARN-5270 at 7/7/16 9:30 PM: --- - should the

[jira] [Comment Edited] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366807#comment-15366807 ] Jian He edited comment on YARN-5270 at 7/7/16 9:31 PM: --- - should the

[jira] [Commented] (YARN-5337) Dshell AM failed with "java.lang.OutOfMemoryError: GC overhead limit exceeded"

[ https://issues.apache.org/jira/browse/YARN-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366828#comment-15366828 ] Jian He commented on YARN-5337: --- Checked many things, the only thing I noticed is that the d

[jira] [Updated] (YARN-5337) Dshell AM failed with "java.lang.OutOfMemoryError: GC overhead limit exceeded"

[ https://issues.apache.org/jira/browse/YARN-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5337: -- Attachment: YARN-5337.1.patch bump the default xmx to be 100mb, also added a log message to help debugging > Ds

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368569#comment-15368569 ] Jian He commented on YARN-5270: --- lgtm, [~kasha], want to look at the latest patch ? we want

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371728#comment-15371728 ] Jian He commented on YARN-5270: --- lgtm, +1 > Solve miscellaneous issues caused by YARN-4844 >

[jira] [Commented] (YARN-5382) RM does not audit log kill request for active applications

[ https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383240#comment-15383240 ] Jian He commented on YARN-5382: --- How about move the audit log in RMApp#AppKilledTransition to

[jira] [Commented] (YARN-4464) default value of yarn.resourcemanager.state-store.max-completed-applications should lower.

[ https://issues.apache.org/jira/browse/YARN-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385319#comment-15385319 ] Jian He commented on YARN-4464: --- I vote for 3) which can solve the slowness problem and prese

[jira] [Commented] (YARN-4464) default value of yarn.resourcemanager.state-store.max-completed-applications should lower.

[ https://issues.apache.org/jira/browse/YARN-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385320#comment-15385320 ] Jian He commented on YARN-4464: --- I vote for 3) which can solve the slowness problem and prese

[jira] [Commented] (YARN-4464) default value of yarn.resourcemanager.state-store.max-completed-applications should lower.

[ https://issues.apache.org/jira/browse/YARN-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386906#comment-15386906 ] Jian He commented on YARN-4464: --- IIUC, the {{rm.max-completed-apps}} controls the number of a

[jira] [Commented] (YARN-5043) TestAMRestart.testRMAppAttemptFailuresValidityInterval random fail

[ https://issues.apache.org/jira/browse/YARN-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387169#comment-15387169 ] Jian He commented on YARN-5043: --- [~hex108], what was the reason for this failure ? > TestAMR

[jira] [Commented] (YARN-5333) Some recovered apps are put into default queue when RM HA

[ https://issues.apache.org/jira/browse/YARN-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389022#comment-15389022 ] Jian He commented on YARN-5333: --- If the initialization of active services is done before star

[jira] [Commented] (YARN-4464) default value of yarn.resourcemanager.state-store.max-completed-applications should lower.

[ https://issues.apache.org/jira/browse/YARN-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390935#comment-15390935 ] Jian He commented on YARN-4464: --- My opinion was that restart scenario occurs so rarely that h

[jira] [Commented] (YARN-4464) default value of yarn.resourcemanager.state-store.max-completed-applications should lower.

[ https://issues.apache.org/jira/browse/YARN-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391220#comment-15391220 ] Jian He commented on YARN-4464: --- sure, sounds good. > default value of yarn.resourcemanager.

<    1   2   3   4   5   6   7   8   9   10   >