[jira] [Commented] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101971#comment-14101971 ] Beckham007 commented on YARN-1856: -- We had work on this for a few days. We will validate

[jira] [Commented] (YARN-1801) NPE in public localizer

[ https://issues.apache.org/jira/browse/YARN-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103649#comment-14103649 ] Beckham007 commented on YARN-1801: -- When something got wrong with hdfs, this error would

[jira] [Commented] (YARN-1800) YARN NodeManager with java.util.concurrent.RejectedExecutionException

[ https://issues.apache.org/jira/browse/YARN-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103700#comment-14103700 ] Beckham007 commented on YARN-1800: -- [~vinodkv] [~jlowe] [~vvasudev] I think we shouldn't

[jira] [Commented] (YARN-1801) NPE in public localizer

[ https://issues.apache.org/jira/browse/YARN-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104921#comment-14104921 ] Beckham007 commented on YARN-1801: -- [~jlowe] we use hadoop 2.2.0. We got both problems in

[jira] [Commented] (YARN-1801) NPE in public localizer

[ https://issues.apache.org/jira/browse/YARN-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14106306#comment-14106306 ] Beckham007 commented on YARN-1801: -- Agree with [~jlowe] NPE in public localizer

[jira] [Commented] (YARN-2440) Cgroups should allow YARN containers to be limited to allocated cores

[ https://issues.apache.org/jira/browse/YARN-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110227#comment-14110227 ] Beckham007 commented on YARN-2440: -- Hi, all Why not use the cpuset subsystem of cgroups?

[jira] [Commented] (YARN-810) Support CGroup ceiling enforcement on CPU

[ https://issues.apache.org/jira/browse/YARN-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110354#comment-14110354 ] Beckham007 commented on YARN-810: - Hi, [~ywskycn] and [~vvasudev]. Both this issue and

[jira] [Commented] (YARN-2454) The function compareTo of variable UNBOUNDED in org.apache.hadoop.yarn.util.resource.Resources is definited wrong.

[ https://issues.apache.org/jira/browse/YARN-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110388#comment-14110388 ] Beckham007 commented on YARN-2454: -- The compareTo() of Resource UNBOUNDED is copied from

[jira] [Updated] (YARN-2454) The function compareTo of variable UNBOUNDED in org.apache.hadoop.yarn.util.resource.Resources is definited wrong.

[ https://issues.apache.org/jira/browse/YARN-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beckham007 updated YARN-2454: - Labels: (was: patch) The function compareTo of variable UNBOUNDED in

[jira] [Updated] (YARN-2454) The function compareTo of variable UNBOUNDED in org.apache.hadoop.yarn.util.resource.Resources is definited wrong.

[ https://issues.apache.org/jira/browse/YARN-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beckham007 updated YARN-2454: - Attachment: YARN-2454-patch.diff The function compareTo of variable UNBOUNDED in

[jira] [Commented] (YARN-2454) The function compareTo of variable UNBOUNDED in org.apache.hadoop.yarn.util.resource.Resources is definited wrong.

[ https://issues.apache.org/jira/browse/YARN-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110410#comment-14110410 ] Beckham007 commented on YARN-2454: -- Hi, [~ozawa]. It could be

[jira] [Commented] (YARN-2454) The function compareTo of variable UNBOUNDED in org.apache.hadoop.yarn.util.resource.Resources is definited wrong.

[ https://issues.apache.org/jira/browse/YARN-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110423#comment-14110423 ] Beckham007 commented on YARN-2454: -- I have talked with [~yxls123123], he will update this

[jira] [Commented] (YARN-2440) Cgroups should allow YARN containers to be limited to allocated cores

[ https://issues.apache.org/jira/browse/YARN-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110566#comment-14110566 ] Beckham007 commented on YARN-2440: -- hi, [~vvasudev] “Cpusets provide a mechanism for

[jira] [Commented] (YARN-2440) Cgroups should allow YARN containers to be limited to allocated cores

[ https://issues.apache.org/jira/browse/YARN-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110567#comment-14110567 ] Beckham007 commented on YARN-2440: -- In addition, mesos uses cpuset for default.

[jira] [Commented] (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 a

[ https://issues.apache.org/jira/browse/YARN-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14115011#comment-14115011 ] Beckham007 commented on YARN-2470: -- Could u give some logs about this? A high value for

[jira] [Created] (YARN-2686) CgroupsLCEResourcesHandler does not support the default Redhat 7/CentOS 7

Beckham007 created YARN-2686: Summary: CgroupsLCEResourcesHandler does not support the default Redhat 7/CentOS 7 Key: YARN-2686 URL: https://issues.apache.org/jira/browse/YARN-2686 Project: Hadoop YARN

[jira] [Commented] (YARN-2686) CgroupsLCEResourcesHandler does not support the default Redhat 7/CentOS 7

[ https://issues.apache.org/jira/browse/YARN-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171851#comment-14171851 ] Beckham007 commented on YARN-2686: -- [~ywskycn] looking forward for the patach. Should we

[jira] [Commented] (YARN-2194) Add Cgroup support for RedHat 7

[ https://issues.apache.org/jira/browse/YARN-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177823#comment-14177823 ] Beckham007 commented on YARN-2194: -- startSystemdSlice/stopSystemdSlice needs root

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030175#comment-14030175 ] Beckham007 commented on YARN-2140: -- I think it could use the net_cls subsystem of cgroup

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030264#comment-14030264 ] Beckham007 commented on YARN-2140: -- tc class add dev ${net_dev} parent ${parent_classid}

[jira] [Created] (YARN-2169) NMSimulator of sls should catch more Exception

Beckham007 created YARN-2169: Summary: NMSimulator of sls should catch more Exception Key: YARN-2169 URL: https://issues.apache.org/jira/browse/YARN-2169 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-2169) NMSimulator of sls should catch more Exception

[ https://issues.apache.org/jira/browse/YARN-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beckham007 updated YARN-2169: - Attachment: YARN-2169.patch NMSimulator of sls should catch more Exception

[jira] Beckham007 shared YARN-2169: NMSimulator of sls should catch more Exception with you

Beckham007 shared an issue with you -- NMSimulator of sls should catch more Exception -- Key: YARN-2169 URL: https://issues.apache.org/jira/browse/YARN-2169

[jira] [Commented] (YARN-2194) Add Cgroup support for RedHat 7

[ https://issues.apache.org/jira/browse/YARN-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049593#comment-14049593 ] Beckham007 commented on YARN-2194: -- +1. A new LCEResourceHandler is needed. To support

[jira] [Commented] (YARN-2466) Umbrella issue for Yarn launched Docker Containers

[ https://issues.apache.org/jira/browse/YARN-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14288615#comment-14288615 ] Beckham007 commented on YARN-2466: -- We use YARN-2718 for this. Umbrella issue for Yarn

[jira] [Created] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

Beckham007 created YARN-3080: Summary: The DockerContainerExecutor could not write the right pid to container pidFile Key: YARN-3080 URL: https://issues.apache.org/jira/browse/YARN-3080 Project: Hadoop

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14342995#comment-14342995 ] Beckham007 commented on YARN-3080: -- We can use yarn containerId as docker container name.

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343000#comment-14343000 ] Beckham007 commented on YARN-3080: -- [~vvasudev] the kill -9 couldn't work in this

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14342994#comment-14342994 ] Beckham007 commented on YARN-3080: -- We can use yarn containerId as docker container name.

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14342996#comment-14342996 ] Beckham007 commented on YARN-3080: -- We can use yarn containerId as docker container name.

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14342613#comment-14342613 ] Beckham007 commented on YARN-3080: -- Getting getting the actual PID from docker inspect is

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14342760#comment-14342760 ] Beckham007 commented on YARN-3080: -- Sorry for mistaking. The pidfile has two functions. 1.