[ 
https://issues.apache.org/jira/browse/YARN-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846201#comment-17846201
 ] 

ASF GitHub Bot commented on YARN-11692:
---------------------------------------

p-szucs commented on code in PR #6821:
URL: https://github.com/apache/hadoop/pull/6821#discussion_r1599502676


##########
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml:
##########
@@ -2087,6 +2087,20 @@
     <name>yarn.nodemanager.linux-container-executor.cgroups.mount-path</name>
   </property>
 
+  <property>
+    <description>This property sets the mount path for CGroups v2.
+      This parameter is optional, and needed to be set only in mixed mode,
+      when CGroups v2 is mounted in a different path than Cgroups v1.
+      For example, in hybrid mode, CGroups v1 controllers can be mounted in
+      /sys/fs/cgroup, while v2 can be mounted in /sys/fs/cgroup/unified folder.

Review Comment:
   It happened to be a bit misleading indeed, I fixed the phrasing. Thanks for 
the suggestion!





> Support mixed cgroup v1/v2 controller structure
> -----------------------------------------------
>
>                 Key: YARN-11692
>                 URL: https://issues.apache.org/jira/browse/YARN-11692
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Benjamin Teke
>            Assignee: Peter Szucs
>            Priority: Major
>              Labels: pull-request-available
>
> There were heavy changes on the device side in cgroup v2. To keep supporting 
> FGPAs and GPUs short term, mixed structures where some of the cgroup 
> controllers are from v1 while others from v2 should be supported. More info: 
> https://dropbear.xyz/2023/05/23/devices-with-cgroup-v2/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to