[jira] [Commented] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16410365#comment-16410365 ] Jim Brennan commented on YARN-6830: --- One question about [~aw]'s approach - while this would solve the

[jira] [Commented] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408656#comment-16408656 ] Jim Brennan commented on YARN-6830: --- There was some discussion of this at the latest docker sync-up

[jira] [Commented] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

[ https://issues.apache.org/jira/browse/YARN-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408627#comment-16408627 ] Jim Brennan commented on YARN-8029: --- Submitted a new patch that fixes the checkstyle issue.   >

[jira] [Updated] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

[ https://issues.apache.org/jira/browse/YARN-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-8029: -- Attachment: YARN-8029.002.patch > YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as

[jira] [Commented] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408136#comment-16408136 ] Jim Brennan commented on YARN-6830: --- I submitted a patch for [YARN-8029], which is an alternative

[jira] [Commented] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

[ https://issues.apache.org/jira/browse/YARN-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408132#comment-16408132 ] Jim Brennan commented on YARN-8029: --- Note, this patch should be considered an alternative to the patch

[jira] [Assigned] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

[ https://issues.apache.org/jira/browse/YARN-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan reassigned YARN-8029: - Assignee: Jim Brennan I've put up a patch for this that changes the delimiter for the docker

[jira] [Updated] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

[ https://issues.apache.org/jira/browse/YARN-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-8029: -- Attachment: YARN-8029.001.patch > YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as

[jira] [Commented] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407924#comment-16407924 ] Jim Brennan commented on YARN-6830: --- I think this patch is ready for review. As I said above, this patch

[jira] [Commented] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407115#comment-16407115 ] Jim Brennan commented on YARN-6830: --- I realized that I forgot to strip enclosing quotes for 

[jira] [Updated] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-6830: -- Attachment: YARN-6830.004.patch > Support quoted strings for environment variables >

[jira] [Commented] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406857#comment-16406857 ] Jim Brennan commented on YARN-6830: --- [~shaneku...@gmail.com], I assigned this to me so I could move it

[jira] [Assigned] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan reassigned YARN-6830: - Assignee: Jim Brennan (was: Shane Kumpf) > Support quoted strings for environment variables >

[jira] [Commented] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406837#comment-16406837 ] Jim Brennan commented on YARN-6830: --- Submitted a new patch that fixes the checkstyle issues. > Support

[jira] [Updated] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-6830: -- Attachment: YARN-6830.003.patch > Support quoted strings for environment variables >

[jira] [Commented] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

[ https://issues.apache.org/jira/browse/YARN-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406628#comment-16406628 ] Jim Brennan commented on YARN-8029: --- I put up a new patch for YARN-6830, to get the discussion going

[jira] [Updated] (YARN-6830) Support quoted strings for environment variables

[ https://issues.apache.org/jira/browse/YARN-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-6830: -- Attachment: YARN-6830.002.patch > Support quoted strings for environment variables >

[jira] [Commented] (YARN-8027) Setting hostname of docker container breaks for --net=host in docker 1.13

[ https://issues.apache.org/jira/browse/YARN-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16399355#comment-16399355 ] Jim Brennan commented on YARN-8027: --- [~suma.shivaprasad], thanks for your comment.  It sounds like the

[jira] [Commented] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

[ https://issues.apache.org/jira/browse/YARN-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16399240#comment-16399240 ] Jim Brennan commented on YARN-8029: --- Thanks [~shaneku...@gmail.com]. This does appear to be a duplicate

[jira] [Commented] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

[ https://issues.apache.org/jira/browse/YARN-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16399006#comment-16399006 ] Jim Brennan commented on YARN-8029: --- There was a related discussion in [HADOOP-11640] about allowing the

[jira] [Created] (YARN-8029) YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators

Jim Brennan created YARN-8029: - Summary: YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS should not use commas as separators Key: YARN-8029 URL: https://issues.apache.org/jira/browse/YARN-8029 Project: Hadoop YARN

[jira] [Commented] (YARN-8027) Setting hostname of docker container breaks for --net=host in docker 1.13

[ https://issues.apache.org/jira/browse/YARN-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398752#comment-16398752 ] Jim Brennan commented on YARN-8027: --- My thinking was that the only known case where there is a problem is

[jira] [Commented] (YARN-8027) Setting hostname of docker container breaks for --net=host in docker 1.13

[ https://issues.apache.org/jira/browse/YARN-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398635#comment-16398635 ] Jim Brennan commented on YARN-8027: --- The unit test failure (testKillOpportunisticForGuaranteedContainer)

[jira] [Updated] (YARN-8027) Setting hostname of docker container breaks for --net=host in docker 1.13

[ https://issues.apache.org/jira/browse/YARN-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-8027: -- Attachment: YARN-8027.001.patch > Setting hostname of docker container breaks for --net=host in docker

[jira] [Commented] (YARN-8027) Setting hostname of docker container breaks for --net=host in docker 1.13

[ https://issues.apache.org/jira/browse/YARN-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397007#comment-16397007 ] Jim Brennan commented on YARN-8027: --- {quote}We should look into whether it is a bug in that version of

[jira] [Commented] (YARN-8027) Setting hostname of docker container breaks for --net=host in docker 1.13

[ https://issues.apache.org/jira/browse/YARN-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396115#comment-16396115 ] Jim Brennan commented on YARN-8027: --- This code was added by [YARN-6804]. [~billie.rinaldi], [~jianh], I

[jira] [Created] (YARN-8027) Setting hostname of docker container breaks for --net=host in docker 1.13

Jim Brennan created YARN-8027: - Summary: Setting hostname of docker container breaks for --net=host in docker 1.13 Key: YARN-8027 URL: https://issues.apache.org/jira/browse/YARN-8027 Project: Hadoop YARN

[jira] [Commented] (YARN-7654) Support ENTRY_POINT for docker container

[ https://issues.apache.org/jira/browse/YARN-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384032#comment-16384032 ] Jim Brennan commented on YARN-7654: --- {quote} 1. Dockerfile describes ENV variables, they are the default

[jira] [Commented] (YARN-7654) Support ENTRY_POINT for docker container

[ https://issues.apache.org/jira/browse/YARN-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383939#comment-16383939 ] Jim Brennan commented on YARN-7654: --- {quote}But how do you differentiate between user-defined variables

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381129#comment-16381129 ] Jim Brennan commented on YARN-7677: --- Check-style issues are expected, as noted above.  Unit test failure

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381033#comment-16381033 ] Jim Brennan commented on YARN-7677: --- Uploaded another patch that fixes the extra import reported by

[jira] [Updated] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7677: -- Attachment: YARN-7677.007.patch > Docker image cannot set HADOOP_CONF_DIR >

[jira] [Updated] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7677: -- Attachment: YARN-7677.006.patch > Docker image cannot set HADOOP_CONF_DIR >

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380382#comment-16380382 ] Jim Brennan commented on YARN-7677: --- [~eyang] the user cannot override the variables that are explicitly

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379347#comment-16379347 ] Jim Brennan commented on YARN-7677: --- {quote}What variables are set explicitly by NM?{quote} Primarily

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377034#comment-16377034 ] Jim Brennan commented on YARN-7677: --- Now that YARN-5714 has been resolved, we have two options for

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373444#comment-16373444 ] Jim Brennan commented on YARN-5714: --- This patch is ready for review. > ContainerExecutor does not order

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373113#comment-16373113 ] Jim Brennan commented on YARN-5714: --- I believe this patch is now ready for review.   >

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373045#comment-16373045 ] Jim Brennan commented on YARN-5714: --- Original version of path.008 did not include the checkstyle fixes. 

[jira] [Updated] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-5714: -- Attachment: YARN-5714.009.patch > ContainerExecutor does not order environment map >

[jira] [Updated] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-5714: -- Attachment: YARN-5714.008.patch > ContainerExecutor does not order environment map >

[jira] [Updated] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-5714: -- Attachment: (was: YARN-5714.008.patch) > ContainerExecutor does not order environment map >

[jira] [Updated] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-5714: -- Attachment: YARN-5714.008.patch > ContainerExecutor does not order environment map >

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372939#comment-16372939 ] Jim Brennan commented on YARN-5714: --- Uploaded a new patch that addresses the check-style issues. >

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372162#comment-16372162 ] Jim Brennan commented on YARN-5714: --- As this has become a blocking issue for YARN-7677, I took the

[jira] [Updated] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-5714: -- Attachment: YARN-5714.007.patch > ContainerExecutor does not order environment map >

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369205#comment-16369205 ] Jim Brennan commented on YARN-7677: --- Agreed. Without this patch, the ordering of variables in the

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365721#comment-16365721 ] Jim Brennan commented on YARN-7677: --- [~jlowe], do you agree about the CLASSPATH for windows?  Let me know

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364945#comment-16364945 ] Jim Brennan commented on YARN-7677: --- {quote}I noticed that sanitizeWindowsEnv no longer adds CLASSPATH to

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364778#comment-16364778 ] Jim Brennan commented on YARN-7677: --- The remaining check-style issue is for adding an 8th parameter to 

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364652#comment-16364652 ] Jim Brennan commented on YARN-7677: --- Uploaded another patch with updates based on [~jlowe]'s review. >

[jira] [Updated] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7677: -- Attachment: YARN-7677.005.patch > Docker image cannot set HADOOP_CONF_DIR >

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363006#comment-16363006 ] Jim Brennan commented on YARN-7677: --- Thanks for the review!  I will address these issues and put up a new

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362696#comment-16362696 ] Jim Brennan commented on YARN-7677: --- I believe these are intermittent failures: {noformat} ERROR]

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362445#comment-16362445 ] Jim Brennan commented on YARN-7677: --- I submitted a new patch that addresses some of the style-check

[jira] [Updated] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7677: -- Attachment: YARN-7677.004.patch > Docker image cannot set HADOOP_CONF_DIR >

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361418#comment-16361418 ] Jim Brennan commented on YARN-7677: --- I've put up another patch for this that addresses the ordering

[jira] [Updated] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7677: -- Attachment: YARN-7677.003.patch > Docker image cannot set HADOOP_CONF_DIR >

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352816#comment-16352816 ] Jim Brennan commented on YARN-7857: --- [~miklos.szeg...@cloudera.com] I have prepared another patch that

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350833#comment-16350833 ] Jim Brennan commented on YARN-7857: --- Thanks [~miklos.szeg...@cloudera.com]! That is a good suggestion. I

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350500#comment-16350500 ] Jim Brennan commented on YARN-7677: --- Thanks everyone! I will work on a new patch using this approach.

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349410#comment-16349410 ] Jim Brennan commented on YARN-7857: --- As this is a change to the command line for container-executor, it

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349305#comment-16349305 ] Jim Brennan commented on YARN-7677: --- I have tested a version of the patch where I write out the

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349168#comment-16349168 ] Jim Brennan commented on YARN-7677: --- Agreed - given that we are just processing the hash map in order, it

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349117#comment-16349117 ] Jim Brennan commented on YARN-7677: --- Thanks [~shaneku...@gmail.com] and [~billie.rinaldi], I will try out

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349024#comment-16349024 ] Jim Brennan commented on YARN-7677: --- [~shaneku...@gmail.com], [~jlowe], [~ebadger] I have verified that

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348898#comment-16348898 ] Jim Brennan commented on YARN-7677: --- [~shaneku...@gmail.com], I am trying to repro locally. In my dev

[jira] [Updated] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7857: -- Attachment: YARN-7857.001.patch > -fstack-check compilation flag causes binary incompatibility for >

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348795#comment-16348795 ] Jim Brennan commented on YARN-7677: --- [~shaneku...@gmail.com] are you running with docker? > Docker image

[jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348684#comment-16348684 ] Jim Brennan commented on YARN-7677: --- Thanks [~jlowe] I will put up a patch for branch-2. > Docker image

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347175#comment-16347175 ] Jim Brennan commented on YARN-7857: --- Thanks [~miklos.szeg...@cloudera.com] for the detailed analysis! I

[jira] [Issue Comment Deleted] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7857: -- Comment: was deleted (was: The SIGSEGV reported in this Jira is a result of compiling with 

[jira] [Issue Comment Deleted] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7857: -- Comment: was deleted (was: The {{-fcheck-stack}} flag was introduced by this Jira.) > -fstack-check

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345776#comment-16345776 ] Jim Brennan commented on YARN-7857: --- The SIGSEGV reported in this Jira is a result of compiling with 

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345771#comment-16345771 ] Jim Brennan commented on YARN-7857: --- The {{-fcheck-stack}} flag was introduced by this Jira. >

[jira] [Commented] (YARN-6721) container-executor should have stack checking

[ https://issues.apache.org/jira/browse/YARN-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345362#comment-16345362 ] Jim Brennan commented on YARN-6721: --- I've filed a new Jira for this compatibility issue: YARN-7857 >

[jira] [Commented] (YARN-7796) Container-executor fails with segfault on certain OS configurations

[ https://issues.apache.org/jira/browse/YARN-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345361#comment-16345361 ] Jim Brennan commented on YARN-7796: --- I've filed a new Jira for this binary compatibility issue: YARN-7857

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345356#comment-16345356 ] Jim Brennan commented on YARN-7857: --- Also see the discussion in the comments in YARN-7796 >

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345354#comment-16345354 ] Jim Brennan commented on YARN-7857: --- I've also verified this with a simple test program that just does

[jira] [Commented] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345341#comment-16345341 ] Jim Brennan commented on YARN-7857: --- This redhat link suggests that there are problems with stack-check:

[jira] [Created] (YARN-7857) -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7

Jim Brennan created YARN-7857: - Summary: -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7 Key: YARN-7857 URL:

[jira] [Updated] (YARN-7677) HADOOP_CONF_DIR should not be automatically put in task environment

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7677: -- Attachment: YARN-7677.002.patch > HADOOP_CONF_DIR should not be automatically put in task environment >

[jira] [Commented] (YARN-7677) HADOOP_CONF_DIR should not be automatically put in task environment

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345301#comment-16345301 ] Jim Brennan commented on YARN-7677: --- I believe the unit test failure

[jira] [Commented] (YARN-7677) HADOOP_CONF_DIR should not be automatically put in task environment

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344137#comment-16344137 ] Jim Brennan commented on YARN-7677: --- Based on the discussion here and in YARN-7226, and after discussing

[jira] [Updated] (YARN-7677) HADOOP_CONF_DIR should not be automatically put in task environment

[ https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7677: -- Attachment: YARN-7677.001.patch > HADOOP_CONF_DIR should not be automatically put in task environment >

[jira] [Commented] (YARN-7796) Container-executor fails with segfault on certain OS configurations

[ https://issues.apache.org/jira/browse/YARN-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343452#comment-16343452 ] Jim Brennan commented on YARN-7796: --- [~miklos.szeg...@cloudera.com] - I believe the max stack size

[jira] [Commented] (YARN-7796) Container-executor fails with segfault on certain OS configurations

[ https://issues.apache.org/jira/browse/YARN-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341628#comment-16341628 ] Jim Brennan commented on YARN-7796: --- [~grepas] that is interesting.  I wonder if it is the version of gcc

[jira] [Commented] (YARN-6721) container-executor should have stack checking

[ https://issues.apache.org/jira/browse/YARN-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340132#comment-16340132 ] Jim Brennan commented on YARN-6721: --- The segmentation fault in container-executor reported in -YARN-7796- 

[jira] [Commented] (YARN-7796) Container-executor fails with segfault on certain OS configurations

[ https://issues.apache.org/jira/browse/YARN-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340101#comment-16340101 ] Jim Brennan commented on YARN-7796: --- We ran into this same issue when running a container-executor that

[jira] [Commented] (YARN-7678) Ability to enable logging of container memory stats

[ https://issues.apache.org/jira/browse/YARN-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311491#comment-16311491 ] Jim Brennan commented on YARN-7678: --- The unit test failure in TestContainerSchedulerQueuing is unrelated

[jira] [Updated] (YARN-7678) Ability to enable logging of container memory stats

[ https://issues.apache.org/jira/browse/YARN-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7678: -- Attachment: YARN-7678-branch-2.001.patch Providing patch for branch-2. Repeated manual tests described

[jira] [Commented] (YARN-7678) Ability to enable logging of container memory stats

[ https://issues.apache.org/jira/browse/YARN-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310302#comment-16310302 ] Jim Brennan commented on YARN-7678: --- Will do. Thanks! > Ability to enable logging of container memory

[jira] [Commented] (YARN-7678) Logging of container memory stats is missing in 2.8

[ https://issues.apache.org/jira/browse/YARN-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300442#comment-16300442 ] Jim Brennan commented on YARN-7678: --- Did not add a new automated test because this just changes the

[jira] [Updated] (YARN-7678) Logging of container memory stats is missing in 2.8

[ https://issues.apache.org/jira/browse/YARN-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7678: -- Attachment: YARN-7678.001.patch Uploading patch for testing. Tested locally by running unit tests and

[jira] [Created] (YARN-7678) Logging of container memory stats is missing in 2.8

Jim Brennan created YARN-7678: - Summary: Logging of container memory stats is missing in 2.8 Key: YARN-7678 URL: https://issues.apache.org/jira/browse/YARN-7678 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-7595) Container launching code suppresses close exceptions after writes

[ https://issues.apache.org/jira/browse/YARN-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292968#comment-16292968 ] Jim Brennan commented on YARN-7595: --- I believe these junit test failures are not related to this patch. I

[jira] [Updated] (YARN-7595) Container launching code suppresses close exceptions after writes

[ https://issues.apache.org/jira/browse/YARN-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7595: -- Attachment: YARN-7595-branch-2.8.002.patch Submitting a new branch-2.8 patch that fixes the checkstyle

[jira] [Updated] (YARN-7595) Container launching code suppresses close exceptions after writes

[ https://issues.apache.org/jira/browse/YARN-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-7595: -- Attachment: YARN-7595-branch-2.8.001.patch Adding a patch for branch-2.8. Ran nodemanager tests locally

[jira] [Commented] (YARN-7595) Container launching code suppresses close exceptions after writes

[ https://issues.apache.org/jira/browse/YARN-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291151#comment-16291151 ] Jim Brennan commented on YARN-7595: --- This is ready for review for branch-2. > Container launching code

[jira] [Reopened] (YARN-7595) Container launching code suppresses close exceptions after writes

[ https://issues.apache.org/jira/browse/YARN-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan reopened YARN-7595: --- Re-opening after adding a patch for branch-2. > Container launching code suppresses close exceptions

<    3   4   5   6   7   8   9   >