You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Shane Kumpf (JIRA)" <ji...@apache.org> on 2018/06/10 16:35:00 UTC
[jira] [Commented] (YARN-8259) Revisit liveliness checks for Docker
containers
[ https://issues.apache.org/jira/browse/YARN-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507437#comment-16507437 ]
Shane Kumpf commented on YARN-8259:
-----------------------------------
[~eyang], [~Jim_Brennan], [~ebadger], [~jlowe] - any additional feedback? I'd like to get this in soon given the impact. It appears the patch that implements #1 still applies if we wanted to go with that for now. We could add alternatives later based on user demand. I want everyone to be comfortable with the approach though. Thanks!
> Revisit liveliness checks for Docker containers
> -----------------------------------------------
>
> Key: YARN-8259
> URL: https://issues.apache.org/jira/browse/YARN-8259
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 3.0.2, 3.2.0, 3.1.1
> Reporter: Shane Kumpf
> Assignee: Shane Kumpf
> Priority: Blocker
> Labels: Docker
> Attachments: YARN-8259.001.patch
>
>
> As privileged containers may execute as a user that does not match the YARN run as user, sending the null signal for liveliness checks could fail. We need to reconsider how liveliness checks are handled in the Docker case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org