[
https://issues.apache.org/jira/browse/YARN-9419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szilard Nemeth updated YARN-9419:
---------------------------------
Fix Version/s: 3.2.2
> Log a warning if GPU isolation is enabled but LinuxContainerExecutor is
> disabled
> --------------------------------------------------------------------------------
>
> Key: YARN-9419
> URL: https://issues.apache.org/jira/browse/YARN-9419
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Szilard Nemeth
> Assignee: Andras Gyori
> Priority: Major
> Fix For: 3.3.0, 3.2.2
>
> Attachments: YARN-9419.001.patch, YARN-9419.002.patch,
> YARN-9419.003.patch, YARN-9419.branch-3.2.001.patch
>
>
> A WARN log should be added at least (logged once on startup) that notifies
> the user about a potentially offending configuration: GPU isolation is
> enabled but LCE is disabled.
> I think this is a dangerous, yet valid configuration: As LCE is the only
> container executor that utilizes cgroups, no real HW-isolation happens if LCE
> is disabled.
> Let's suppose we have 2 GPU devices in 1 node:
> # NM reports 2 devices (as a Resource) to RM
> # RM assigns GPU#1 to container#2 that requests 1 GPU device
> # When container#2 is also requesting 1 GPU device, RM is going to assign
> either GPU#1 or GPU#2, so there's no guarantee that GPU#2 will be assigned.
> If GPU#1 is assigned to a second container, nasty things could happen.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
