[
https://issues.apache.org/jira/browse/STORM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295076#comment-15295076
]
ASF GitHub Bot commented on STORM-1631:
---------------------------------------
Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/1216#issuecomment-220783660
At yahoo, cgroups are used to limit both memory and cpu of every worker so
that topologies can have more resource isolation
On Saturday, May 21, 2016, Xin Wang <[email protected]> wrote:
> @yegortokmakov <https://github.com/yegortokmakov> in general, for one
> topology:
> i:woker number
> worker number < cluster node number
> worker/per node
> ii:thread number
> this depends on your logic. for example, the parallelism of KafkaSpout
> should be equal to the number of partitions, in order to get a good
> performance.
>
> btw, I really recommend you to upgrade your storm to 1.0.1.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/storm/pull/1216#issuecomment-220783029>
>
> storm CGroup bugs 1) when launching workers as the user that submitted the
> topology 2) when initial cleanup of cgroup fails
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: STORM-1631
> URL: https://issues.apache.org/jira/browse/STORM-1631
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Boyang Jerry Peng
> Assignee: Boyang Jerry Peng
> Fix For: 2.0.0
>
>
> In secure multitenant storm, topology workers are launched with permission of
> the user that submitted the topology. This causes a problem with cgroups
> since workers are launched with permissions of the topology user which does
> not have permissions to modify cgroups storm is using
> Also, the clean up code is not trying to clean up cgroups of killed workers
> if the initial attempt failed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
