[
https://issues.apache.org/jira/browse/STORM-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134506#comment-15134506
]
ASF GitHub Bot commented on STORM-1336:
---------------------------------------
Github user knusbaum commented on a diff in the pull request:
https://github.com/apache/storm/pull/1053#discussion_r52045220
--- Diff: storm-core/src/clj/org/apache/storm/daemon/supervisor.clj ---
@@ -344,6 +348,12 @@
:sync-retry (atom 0)
:download-lock (Object.)
:stormid->profiler-actions (atom {})
+ :cgroup-manager (if (conf STORM-CGROUP-ENABLE)
+ (let [cgroup-manager (.newInstance (Class/forName
(conf STORM-RESOURCE-ISOLATION-PLUGIN)))]
--- End diff --
If the resource isolation plugin is pluggable, do we want to call this
`:cgroup-manager`?
> Evalute/Port JStorm cgroup support
> ----------------------------------
>
> Key: STORM-1336
> URL: https://issues.apache.org/jira/browse/STORM-1336
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-core
> Reporter: Robert Joseph Evans
> Assignee: Boyang Jerry Peng
> Labels: jstorm-merger
>
> Supports controlling the upper limit of CPU core usage for a worker using
> cgroups
> Sounds like a good start, will be nice to integrate it with RAS requests too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
