You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/21 08:50:12 UTC

[jira] [Commented] (STORM-1631) storm CGroup bugs 1) when launching workers as the user that submitted the topology 2) when initial cleanup of cgroup fails

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

ASF GitHub Bot commented on STORM-1631:
---------------------------------------

Github user caishize commented on the pull request:

    https://github.com/apache/storm/pull/1216#issuecomment-220766704
  
    is any one using cgroup to limit the cpu usage? these days i found the system will be halt when the pressure is growing up, and i found that much of the cpu was wasted by the system, above 25%
    CentOS 6.5 
    64 bit 
    128 G 
    32 core
    31 workers


> 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)