[
https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362696#comment-16362696
]
Jim Brennan commented on YARN-7677:
-----------------------------------
I believe these are intermittent failures:
{noformat}
ERROR] Failures:
[ERROR] TestContainerManager.testContainerUpgradeRollbackDueToFailure:880 The
Rolled-back process should be a different pid. Actual: 17405
[ERROR]
TestContainerSchedulerQueuing.testKillOpportunisticForGuaranteedContainer:547
expected:<SCHEDULED> but was:<RUNNING>
{noformat}
The check-style issues are due to adding an 8th argument to writeLaunchEnv(),
and ContainerLaunch.call() going over 150 lines. I can remove an empty line to
address that, but I'm not sure it's worth it?
Aside from those issues, I think this Jira is ready to review.
([~jlowe], [~ebadger], [[email protected]], [~billie.rinaldi])
> Docker image cannot set HADOOP_CONF_DIR
> ---------------------------------------
>
> Key: YARN-7677
> URL: https://issues.apache.org/jira/browse/YARN-7677
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Eric Badger
> Assignee: Jim Brennan
> Priority: Major
> Attachments: YARN-7677.001.patch, YARN-7677.002.patch,
> YARN-7677.003.patch, YARN-7677.004.patch
>
>
> Currently, {{HADOOP_CONF_DIR}} is being put into the task environment whether
> it's set by the user or not. It completely bypasses the whitelist and so
> there is no way for a task to not have {{HADOOP_CONF_DIR}} set. This causes
> problems in the Docker use case where Docker containers will set up their own
> environment and have their own {{HADOOP_CONF_DIR}} preset in the image
> itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
