[jira] [Commented] (YARN-11107) When NodeLabel is enabled for a YARN cluster, AM blacklist program does not work properly

[ https://issues.apache.org/jira/browse/YARN-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520360#comment-17520360 ] Junping Du commented on YARN-11107: --- Hi [~zhangxiping], welcome to join Hadoop community for

[jira] [Commented] (YARN-9548) [Umbrella] Make YARN work well in elastic cloud environments

[ https://issues.apache.org/jira/browse/YARN-9548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906068#comment-16906068 ] Junping Du commented on YARN-9548: -- +1. I am quite interesting on autoscaling part. For horizontal

[jira] [Commented] (YARN-999) In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task.

[ https://issues.apache.org/jira/browse/YARN-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766686#comment-16766686 ] Junping Du commented on YARN-999: - bq. I am not sure how exactly the reduction of node resources is

[jira] [Assigned] (YARN-1508) Document Dynamic Resource Configuration feature

[ https://issues.apache.org/jira/browse/YARN-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-1508: Assignee: (was: Junping Du) > Document Dynamic Resource Configuration feature >

[jira] [Commented] (YARN-1508) Document Dynamic Resource Configuration feature

[ https://issues.apache.org/jira/browse/YARN-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765631#comment-16765631 ] Junping Du commented on YARN-1508: -- Sure. I make it unassigned. Thanks for working on this, [~elgoiri]!

[jira] [Assigned] (YARN-6055) ContainersMonitorImpl need be adjusted when NM resource changed.

[ https://issues.apache.org/jira/browse/YARN-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-6055: Assignee: (was: Junping Du) > ContainersMonitorImpl need be adjusted when NM resource changed.

[jira] [Assigned] (YARN-2489) ResouceOption's overcommitTimeout should be respected during resource update on NM

[ https://issues.apache.org/jira/browse/YARN-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-2489: Assignee: (was: Junping Du) > ResouceOption's overcommitTimeout should be respected during

[jira] [Commented] (YARN-999) In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task.

[ https://issues.apache.org/jira/browse/YARN-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765630#comment-16765630 ] Junping Du commented on YARN-999: - bq. I tried to go through the code to see where the overcommit timeout

[jira] [Assigned] (YARN-999) In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task.

[ https://issues.apache.org/jira/browse/YARN-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-999: --- Assignee: (was: Junping Du) > In case of long running tasks, reduce node resource should balloon

[jira] [Assigned] (YARN-1000) Dynamic resource configuration feature can be configured to enable or disable and persistent on setting or not

[ https://issues.apache.org/jira/browse/YARN-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-1000: Assignee: (was: Junping Du) > Dynamic resource configuration feature can be configured to

[jira] [Commented] (YARN-1508) Document Dynamic Resource Configuration feature

[ https://issues.apache.org/jira/browse/YARN-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765617#comment-16765617 ] Junping Du commented on YARN-1508: -- Not yet I think. [~elgoiri], please feel free to take it if you would

[jira] [Updated] (YARN-6091) the AppMaster register failed when use Docker on LinuxContainer

[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6091: - Target Version/s: (was: 2.8.5) > the AppMaster register failed when use Docker on LinuxContainer >

[jira] [Commented] (YARN-5464) Server-Side NM Graceful Decommissioning with RM HA

[ https://issues.apache.org/jira/browse/YARN-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546329#comment-16546329 ] Junping Du commented on YARN-5464: -- sure. unassign it. please feel free to take it. > Server-Side NM

[jira] [Assigned] (YARN-5464) Server-Side NM Graceful Decommissioning with RM HA

[ https://issues.apache.org/jira/browse/YARN-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-5464: Assignee: (was: Junping Du) > Server-Side NM Graceful Decommissioning with RM HA >

[jira] [Commented] (YARN-6265) yarn.resourcemanager.fail-fast is used inconsistently

[ https://issues.apache.org/jira/browse/YARN-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536673#comment-16536673 ] Junping Du commented on YARN-6265: -- Oops... just found my commit message doesn't include jira number...

[jira] [Commented] (YARN-6265) yarn.resourcemanager.fail-fast is used inconsistently

[ https://issues.apache.org/jira/browse/YARN-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529365#comment-16529365 ] Junping Du commented on YARN-6265: -- +1. 003 patch LGTM. Will commit it tomorrow if no further comments

[jira] [Commented] (YARN-6265) yarn.resourcemanager.fail-fast is used inconsistently

[ https://issues.apache.org/jira/browse/YARN-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16527270#comment-16527270 ] Junping Du commented on YARN-6265: -- Looks like patch doesn't apply any more. [~yuanbo] , do you have

[jira] [Commented] (YARN-6265) yarn.resourcemanager.fail-fast is used inconsistently

[ https://issues.apache.org/jira/browse/YARN-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523583#comment-16523583 ] Junping Du commented on YARN-6265: -- sorry for late coming for a while on this. v2 patch LGTM. Let me kick

[jira] [Commented] (YARN-6482) TestSLSRunner runs but doesn't executed jobs (.json parsing issue)

[ https://issues.apache.org/jira/browse/YARN-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523264#comment-16523264 ] Junping Du commented on YARN-6482: -- Hi [~yuanbo], any plan to deliver a fix? > TestSLSRunner runs but

[jira] [Commented] (YARN-6091) the AppMaster register failed when use Docker on LinuxContainer

[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466774#comment-16466774 ] Junping Du commented on YARN-6091: -- Move to 2.8.5 as 2.8.4 is in RC stage. > the AppMaster register

[jira] [Updated] (YARN-6091) the AppMaster register failed when use Docker on LinuxContainer

[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6091: - Target Version/s: 2.8.5 (was: 2.8.4) > the AppMaster register failed when use Docker on LinuxContainer >

[jira] [Commented] (YARN-7598) Document how to use classpath isolation for aux-services in YARN

[ https://issues.apache.org/jira/browse/YARN-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449445#comment-16449445 ] Junping Du commented on YARN-7598: -- +1. Latest patch LGTM. Committing. > Document how to use classpath

[jira] [Updated] (YARN-7598) Document how to use classpath isolation for aux-services in YARN

[ https://issues.apache.org/jira/browse/YARN-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7598: - Target Version/s: 3.2.0, 3.1.1, 2.9.2, 3.0.3 (was: 3.2.0) > Document how to use classpath isolation for

[jira] [Commented] (YARN-7598) Document how to use classpath isolation for aux-services in YARN

[ https://issues.apache.org/jira/browse/YARN-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430229#comment-16430229 ] Junping Du commented on YARN-7598: -- Thanks [~xgong] for the updating the patch! The patch looks generally

[jira] [Commented] (YARN-8118) Better utilize gracefully decommissioning node managers

[ https://issues.apache.org/jira/browse/YARN-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429629#comment-16429629 ] Junping Du commented on YARN-8118: -- Thanks for contributing your idea and code, [~Karthik Palaniappan]!

[jira] [Commented] (YARN-6091) the AppMaster register failed when use Docker on LinuxContainer

[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428154#comment-16428154 ] Junping Du commented on YARN-6091: -- move to 2.8.4 as 2.8.3 is released last year. > the AppMaster

[jira] [Updated] (YARN-6091) the AppMaster register failed when use Docker on LinuxContainer

[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6091: - Target Version/s: 2.8.4 (was: 2.8.3) > the AppMaster register failed when use Docker on LinuxContainer >

[jira] [Commented] (YARN-7598) Document how to use classpath isolation for aux-services in YARN

[ https://issues.apache.org/jira/browse/YARN-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343874#comment-16343874 ] Junping Du commented on YARN-7598: -- Thanks [~vinodkv] for comments. I agree that's a reasonable

[jira] [Updated] (YARN-7468) Provide means for container network policy control

[ https://issues.apache.org/jira/browse/YARN-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7468: - Priority: Major (was: Minor) > Provide means for container network policy control >

[jira] [Commented] (YARN-7598) Document how to use classpath isolation for aux-services in YARN

[ https://issues.apache.org/jira/browse/YARN-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314118#comment-16314118 ] Junping Du commented on YARN-7598: -- +1. Patch LGTM. Will commit it tomorrow if no further review/comments.

[jira] [Commented] (YARN-7673) ClassNotFoundException: org.apache.hadoop.yarn.server.api.DistributedSchedulingAMProtocol when using hadoop-client-minicluster

[ https://issues.apache.org/jira/browse/YARN-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299201#comment-16299201 ] Junping Du commented on YARN-7673: -- Thanks [~zjffdu] for trying hadoop shaded jar in downstream project

[jira] [Commented] (YARN-7466) ResourceRequest has a different default for allocationRequestId than Container

[ https://issues.apache.org/jira/browse/YARN-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16297652#comment-16297652 ] Junping Du commented on YARN-7466: -- Hi [~jianhe] and [~eyang], this problem seems to be generic to

[jira] [Commented] (YARN-7673) ClassNotFoundException: org.apache.hadoop.yarn.server.api.DistributedSchedulingAMProtocol when using hadoop-client-minicluster

[ https://issues.apache.org/jira/browse/YARN-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16297637#comment-16297637 ] Junping Du commented on YARN-7673: -- I think we could miss adding yarn-server-api into dependency of

[jira] [Comment Edited] (YARN-7646) MR job (based on old version tarball) get failed due to incompatible resource request

[ https://issues.apache.org/jira/browse/YARN-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1628#comment-1628 ] Junping Du edited comment on YARN-7646 at 12/13/17 9:58 PM: [~sunilg], my test

[jira] [Commented] (YARN-7646) MR job (based on old version tarball) get failed due to incompatible resource request

[ https://issues.apache.org/jira/browse/YARN-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1628#comment-1628 ] Junping Du commented on YARN-7646: -- [~sunil.gov...@gmail.com], my test here is using MR over distributed

[jira] [Commented] (YARN-7646) MR job (based on old version tarball) get failed due to incompatible resource request

[ https://issues.apache.org/jira/browse/YARN-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289971#comment-16289971 ] Junping Du commented on YARN-7646: -- No different. Still hit the same issue. Below is my configuration of

[jira] [Commented] (YARN-7646) MR job (based on old version tarball) get failed due to incompatible resource request

[ https://issues.apache.org/jira/browse/YARN-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289952#comment-16289952 ] Junping Du commented on YARN-7646: -- I was trying tarball of 2.9.0. Let me try 2.8.3 instead to see any

[jira] [Commented] (YARN-7646) MR job (based on old version tarball) get failed due to incompatible resource request

[ https://issues.apache.org/jira/browse/YARN-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288566#comment-16288566 ] Junping Du commented on YARN-7646: -- CC [~andrew.wang] [~vinodkv], [~jlowe]. > MR job (based on old

[jira] [Created] (YARN-7646) MR job (based on old version tarball) get failed due to incompatible resource request

Junping Du created YARN-7646: Summary: MR job (based on old version tarball) get failed due to incompatible resource request Key: YARN-7646 URL: https://issues.apache.org/jira/browse/YARN-7646 Project:

[jira] [Commented] (YARN-7496) CS Intra-queue preemption user-limit calculations are not in line with LeafQueue user-limit calculations

[ https://issues.apache.org/jira/browse/YARN-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277801#comment-16277801 ] Junping Du commented on YARN-7496: -- Merge to branch-2.8.3 given we previously set fix version to 2.8.3. >

[jira] [Commented] (YARN-7469) Capacity Scheduler Intra-queue preemption: User can starve if newest app is exactly at user limit

[ https://issues.apache.org/jira/browse/YARN-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277799#comment-16277799 ] Junping Du commented on YARN-7469: -- Merge to branch-2.8.3 given we previously set fix version to 2.8.3. >

[jira] [Updated] (YARN-7586) Application Placement should be done before ACL checks in ResourceManager

[ https://issues.apache.org/jira/browse/YARN-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7586: - Target Version/s: 3.1.0 > Application Placement should be done before ACL checks in ResourceManager >

[jira] [Commented] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271586#comment-16271586 ] Junping Du commented on YARN-7558: -- Thanks for reply, Xuan! Agree that this is not easy to add a UT and

[jira] [Commented] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269672#comment-16269672 ] Junping Du commented on YARN-7558: -- Thanks [~nmaheshwari] for reporting the issue and [~xgong] for

[jira] [Updated] (YARN-7558) YARN log command fails to get logs for running containers if the url authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7558: - Target Version/s: 2.9.1, 3.0.1 > YARN log command fails to get logs for running containers if the url >

[jira] [Commented] (YARN-914) (Umbrella) Support graceful decommission of nodemanager

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256106#comment-16256106 ] Junping Du commented on YARN-914: - Client side graceful decommission work has been done together with proper

[jira] [Commented] (YARN-5464) Server-Side NM Graceful Decommissioning with RM HA

[ https://issues.apache.org/jira/browse/YARN-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256093#comment-16256093 ] Junping Du commented on YARN-5464: -- I am working on a design doc for this, will upload for review soon. >

[jira] [Assigned] (YARN-5464) Server-Side NM Graceful Decommissioning with RM HA

[ https://issues.apache.org/jira/browse/YARN-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-5464: Assignee: Junping Du > Server-Side NM Graceful Decommissioning with RM HA >

[jira] [Commented] (YARN-7517) RegistryDNS does not work with secure ZooKeeper

[ https://issues.apache.org/jira/browse/YARN-7517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256033#comment-16256033 ] Junping Du commented on YARN-7517: -- CC [~jianhe], [~billie.rinaldi]. > RegistryDNS does not work with

[jira] [Updated] (YARN-6078) Containers stuck in Localizing state

[ https://issues.apache.org/jira/browse/YARN-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6078: - Fix Version/s: 2.10.0 > Containers stuck in Localizing state > > >

[jira] [Commented] (YARN-6078) Containers stuck in Localizing state

[ https://issues.apache.org/jira/browse/YARN-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252163#comment-16252163 ] Junping Du commented on YARN-6078: -- +1 on branch-2 patch. I have commit the patch to trunk, branch-3.0,

[jira] [Updated] (YARN-6078) Containers stuck in Localizing state

[ https://issues.apache.org/jira/browse/YARN-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6078: - Fix Version/s: 2.9.1 > Containers stuck in Localizing state > > >

[jira] [Commented] (YARN-6078) Containers stuck in Localizing state

[ https://issues.apache.org/jira/browse/YARN-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250478#comment-16250478 ] Junping Du commented on YARN-6078: -- Thanks [~bibinchundatt] for review and comments. +1 on 03 patch as

[jira] [Commented] (YARN-6078) Containers stuck in Localizing state

[ https://issues.apache.org/jira/browse/YARN-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16246713#comment-16246713 ] Junping Du commented on YARN-6078: -- Thanks [~billie.rinaldi] for updating the patch! A quick question

[jira] [Commented] (YARN-5422) ContainerLocalizer log should be logged in separate log file.

[ https://issues.apache.org/jira/browse/YARN-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1624#comment-1624 ] Junping Du commented on YARN-5422: -- CC [~suma.shivaprasad]. Suma, does your previous work of separating

[jira] [Commented] (YARN-7400) incorrect log preview displayed in jobhistory server ui

[ https://issues.apache.org/jira/browse/YARN-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236713#comment-16236713 ] Junping Du commented on YARN-7400: -- Thanks [~subru]. I forget to mark jira as fixed but have commit to

[jira] [Commented] (YARN-7400) incorrect log preview displayed in jobhistory server ui

[ https://issues.apache.org/jira/browse/YARN-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16227508#comment-16227508 ] Junping Du commented on YARN-7400: -- Thanks [~xgong] for delivering the fix. The fix is straightforward, so

[jira] [Commented] (YARN-7400) incorrect log preview displayed in jobhistory server ui

[ https://issues.apache.org/jira/browse/YARN-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225982#comment-16225982 ] Junping Du commented on YARN-7400: -- Hey [~subru], all new format log related patches get landed on 2.9, so

[jira] [Updated] (YARN-7400) incorrect log preview displayed in jobhistory server ui

[ https://issues.apache.org/jira/browse/YARN-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7400: - Target Version/s: 2.9.0, 3.0.0, 3.1.0 > incorrect log preview displayed in jobhistory server ui >

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225652#comment-16225652 ] Junping Du commented on YARN-6930: -- bq. It has to be explicitly turned on in 2.9. In 2.8 it was turned on

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225274#comment-16225274 ] Junping Du commented on YARN-6930: -- Hi [~vvasudev], thanks for comments. It sounds like 2.8.2 and 2.9 have

[jira] [Updated] (YARN-7230) Document DockerContainerRuntime for branch-2.8 with proper scope and claim as an experimental feature

[ https://issues.apache.org/jira/browse/YARN-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7230: - Fix Version/s: 2.8.2 > Document DockerContainerRuntime for branch-2.8 with proper scope and claim as > an

[jira] [Commented] (YARN-7230) Document DockerContainerRuntime for branch-2.8 with proper scope and claim as an experimental feature

[ https://issues.apache.org/jira/browse/YARN-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208254#comment-16208254 ] Junping Du commented on YARN-7230: -- Thanks [~dan...@cloudera.com] and [~ebadger] for review. The patch

[jira] [Commented] (YARN-7333) container-executor fails to remove entries from a directory that is not writable or executable

[ https://issues.apache.org/jira/browse/YARN-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206731#comment-16206731 ] Junping Du commented on YARN-7333: -- Thanks [~jlowe] for the patch and [~nroberts] for review! >

[jira] [Commented] (YARN-7124) LogAggregationTFileController deletes/renames while file is open

[ https://issues.apache.org/jira/browse/YARN-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206360#comment-16206360 ] Junping Du commented on YARN-7124: -- Sorry for coming late on this as just back from vacation. The patch

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16183683#comment-16183683 ] Junping Du commented on YARN-6570: -- Sorry for replying late as on vacation recently and thanks for the

[jira] [Commented] (YARN-7248) NM returns new SCHEDULED container status to older clients

[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16183654#comment-16183654 ] Junping Du commented on YARN-7248: -- I think we should fix this in 3.0-beta also given rolling upgrade from

[jira] [Updated] (YARN-7248) NM returns new SCHEDULED container status to older clients

[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7248: - Target Version/s: 2.9.0 (was: 2.9.0, 3.0.0-beta1) > NM returns new SCHEDULED container status to older

[jira] [Updated] (YARN-7248) NM returns new SCHEDULED container status to older clients

[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7248: - Target Version/s: 2.9.0, 3.0.0-beta1 (was: 2.9.0) > NM returns new SCHEDULED container status to older

[jira] [Commented] (YARN-6509) Add a size threshold beyond which yarn logs will require a force option

[ https://issues.apache.org/jira/browse/YARN-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177580#comment-16177580 ] Junping Du commented on YARN-6509: -- Thanks [~xgong] for updating the patch. v3 patch looks good to me in

[jira] [Commented] (YARN-6623) Add support to turn off launching privileged containers in the container-executor

[ https://issues.apache.org/jira/browse/YARN-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177381#comment-16177381 ] Junping Du commented on YARN-6623: -- Hi [~vvasudev], do you agree with what we discussed in security alias

[jira] [Updated] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6570: - Fix Version/s: (was: 2.8.2) 2.8.3 > No logs were found for running application,

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177219#comment-16177219 ] Junping Du commented on YARN-6570: -- Thanks [~xgong]. Correct it to 2.8.3 for landing on branch-2.8 only.

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177197#comment-16177197 ] Junping Du commented on YARN-6570: -- Findbug is not related to the patch here. I think we are good to go

[jira] [Commented] (YARN-6623) Add support to turn off launching privileged containers in the container-executor

[ https://issues.apache.org/jira/browse/YARN-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175908#comment-16175908 ] Junping Du commented on YARN-6623: -- bq. I plan to commit the patch to trunk/branch-3.0 tomorrow if no more

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175566#comment-16175566 ] Junping Du commented on YARN-6570: -- The failed tests are passed locally. Trigger another run for jenkins

[jira] [Commented] (YARN-6623) Add support to turn off launching privileged containers in the container-executor

[ https://issues.apache.org/jira/browse/YARN-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175386#comment-16175386 ] Junping Du commented on YARN-6623: -- bq. We have already documented that the docker feature is alpha, not

[jira] [Commented] (YARN-7118) AHS REST API can return NullPointerException

[ https://issues.apache.org/jira/browse/YARN-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174047#comment-16174047 ] Junping Du commented on YARN-7118: -- Thanks [~Prabhu Joseph] for reporting the issue and [~billie.rinaldi]

[jira] [Commented] (YARN-7230) Document DockerContainerRuntime for branch-2.8 with proper scope and claim as an experimental feature

[ https://issues.apache.org/jira/browse/YARN-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173891#comment-16173891 ] Junping Du commented on YARN-7230: -- Thanks [~shaneku...@gmail.com]! > Document DockerContainerRuntime for

[jira] [Created] (YARN-7230) Document DockerContainerRuntime for branch-2.8 with proper scope and claim as an experimental feature

Junping Du created YARN-7230: Summary: Document DockerContainerRuntime for branch-2.8 with proper scope and claim as an experimental feature Key: YARN-7230 URL: https://issues.apache.org/jira/browse/YARN-7230

[jira] [Commented] (YARN-6623) Add support to turn off launching privileged containers in the container-executor

[ https://issues.apache.org/jira/browse/YARN-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173795#comment-16173795 ] Junping Du commented on YARN-6623: -- Thanks [~vvasudev] for working hard on this effort and everyone for

[jira] [Commented] (YARN-7034) DefaultLinuxContainerRuntime and DockerLinuxContainerRuntime sends client environment variables to container-executor

[ https://issues.apache.org/jira/browse/YARN-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173515#comment-16173515 ] Junping Du commented on YARN-7034: -- Mark it as blocker given discussions in security thread. >

[jira] [Commented] (YARN-7034) DefaultLinuxContainerRuntime and DockerLinuxContainerRuntime sends client environment variables to container-executor

[ https://issues.apache.org/jira/browse/YARN-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173514#comment-16173514 ] Junping Du commented on YARN-7034: -- Thanks [~miklos.szeg...@cloudera.com] for updating the patch and

[jira] [Updated] (YARN-7034) DefaultLinuxContainerRuntime and DockerLinuxContainerRuntime sends client environment variables to container-executor

[ https://issues.apache.org/jira/browse/YARN-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7034: - Priority: Blocker (was: Critical) > DefaultLinuxContainerRuntime and DockerLinuxContainerRuntime sends

[jira] [Commented] (YARN-7196) Fix finicky TestContainerManager tests

[ https://issues.apache.org/jira/browse/YARN-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172576#comment-16172576 ] Junping Du commented on YARN-7196: -- Sorry for coming late. 002 patch is quite straightforward and LGTM in

[jira] [Updated] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6570: - Attachment: YARN-6570-branch-2.8.002.patch Fix unit test failure and check style warning in 002 patch for

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170800#comment-16170800 ] Junping Du commented on YARN-6570: -- Submit patch to trigger jenkins report. > No logs were found for

[jira] [Updated] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6570: - Attachment: YARN-6570-branch-2.8.001.patch Upload patch for branch-2.8. Basically, adding SCHEDULED

[jira] [Reopened] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reopened YARN-6570: -- > No logs were found for running application, running container >

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170763#comment-16170763 ] Junping Du commented on YARN-6570: -- Thanks [~xgong] for review and commit the patch. I would like to

[jira] [Commented] (YARN-7196) Fix finicky TestContainerManager tests

[ https://issues.apache.org/jira/browse/YARN-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170332#comment-16170332 ] Junping Du commented on YARN-7196: -- Hi [~asuresh], sure. please take it up. :) Sorry for missing your

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168614#comment-16168614 ] Junping Du commented on YARN-6570: -- BTW, TestContainerManager failure get tracked in YARN-7196 > No logs

[jira] [Updated] (YARN-7196) Fix finicky TestContainerManager tests

[ https://issues.apache.org/jira/browse/YARN-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7196: - Attachment: YARN-7196.patch > Fix finicky TestContainerManager tests >

[jira] [Commented] (YARN-7196) Fix finicky TestContainerManager tests

[ https://issues.apache.org/jira/browse/YARN-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168600#comment-16168600 ] Junping Du commented on YARN-7196: -- It failed consistently now, from YARN-6570 to YARN-7034. Take a quick

[jira] [Updated] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6570: - Attachment: YARN-6570-v3.patch Update the patch to fix the test failures in TestEventFlow. The failure of

[jira] [Commented] (YARN-7174) Add retry logic in LogsCLI when fetch running application logs

[ https://issues.apache.org/jira/browse/YARN-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168542#comment-16168542 ] Junping Du commented on YARN-7174: -- got it. v2 patch LGTM. +1. Will commit it shortly. > Add retry logic

[jira] [Updated] (YARN-7174) Add retry logic in LogsCLI when fetch running application logs

[ https://issues.apache.org/jira/browse/YARN-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-7174: - Target Version/s: 2.9.0, 3.1.0 > Add retry logic in LogsCLI when fetch running application logs >

[jira] [Commented] (YARN-7162) Remove XML excludes file format

[ https://issues.apache.org/jira/browse/YARN-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167210#comment-16167210 ] Junping Du commented on YARN-7162: -- bq. Given that code freeze for Hadoop 3 beta 1 is tomorrow (Sept 15),

[jira] [Commented] (YARN-7162) Remove XML excludes file format

[ https://issues.apache.org/jira/browse/YARN-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167043#comment-16167043 ] Junping Du commented on YARN-7162: -- bq. Maybe we do want to support the old format, JSON, and XML, but we

[jira] [Commented] (YARN-7162) Remove XML excludes file format

[ https://issues.apache.org/jira/browse/YARN-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167024#comment-16167024 ] Junping Du commented on YARN-7162: -- bq. if you wanted to have nodeA do 50, nodeB do 70, etc, you can't do

  1   2   3   4   5   6   7   8   9   10   >