You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by caishize <gi...@git.apache.org> on 2016/05/31 15:58:09 UTC
[GitHub] storm pull request: [STORM-1631] - Storm CGroup bugs 1) when launching worke...
Github user caishize commented on the pull request:
https://github.com/apache/storm/pull/1216
I\u2019ve found that the system will be halt when there are some workers are reboot frequently, this may be a bug of the OS\uff0cand i found this https://bugs.centos.org/view.php?id=7538 may be the reason, i hadn\u2019t confirm this yet..
Darwin
On May 21, 2016, at 11:25 PM, Boyang Jerry Peng <no...@github.com>> wrote:
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 <no...@github.com>> 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.
>
> \u2014
> 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>
>
\u2014
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub<https://github.com/apache/storm/pull/1216#issuecomment-220783660>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---