[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
----------------------------
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate different types of resource (CPU, onheap-memory, offheap-memory) to
the workers assigned to each topology's tasks.
However, such resources are not visible to the supervisor, therefore,
supervisor will still launch workers with fixed amount of heap size memory
(e.g., -Xmx=768M).
Therefore, we need to a whole set of scheme that allow nimbus to put different
types of resources to each worker slot, then push the resources with assignment
to ZooKeepers; also, at the supervisor side, such resources in each worker slot
should be used by supervisor for launching a worker's JVM.
Such scheme can be used not only by RAS scheduler (STORM-893), but also by any
customized scheduler for conducting mem/cpu resource aware scheduling.
In the future, the resources of memory, CPU and network can also be used by
supervisor to launch a worker in a resource-segregated container, such as a
CGroup or Docker.
was:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate different types of resource (CPU, onheap-memory, offheap-memory) to
the workers assigned to each topology's tasks.
However, such resources are not visible to the supervisor, therefore,
supervisor will still launch workers with fixed amount of heap size memory
(e.g., -Xmx=768M).
Therefore, we need to a whole set of scheme that allow nimbus to put different
types of resources to each worker slot, then push the resources with assignment
to ZooKeepers; also, at the supervisor side, such resources in each worker slot
should be used by supervisor for launching a worker's JVM.
Such scheme can be used not only by RAS scheduler (STORM-893), but also be used
by any customized scheduler for conducting mem/cpu resource aware scheduling.
In the future, the resources of memory, CPU and network can also be used by
supervisor to launch a worker in a resource-segregated container, such as a
CGroup or Docker.
> Launching Workers with resources specified in resource-aware schedulers
> -----------------------------------------------------------------------
>
> Key: STORM-1093
> URL: https://issues.apache.org/jira/browse/STORM-1093
> Project: Apache Storm
> Issue Type: Story
> Components: storm-core
> Reporter: Zhuo Liu
> Assignee: Zhuo Liu
>
> Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
> allocate different types of resource (CPU, onheap-memory, offheap-memory) to
> the workers assigned to each topology's tasks.
> However, such resources are not visible to the supervisor, therefore,
> supervisor will still launch workers with fixed amount of heap size memory
> (e.g., -Xmx=768M).
> Therefore, we need to a whole set of scheme that allow nimbus to put
> different types of resources to each worker slot, then push the resources
> with assignment to ZooKeepers; also, at the supervisor side, such resources
> in each worker slot should be used by supervisor for launching a worker's JVM.
> Such scheme can be used not only by RAS scheduler (STORM-893), but also by
> any customized scheduler for conducting mem/cpu resource aware scheduling.
> In the future, the resources of memory, CPU and network can also be used by
> supervisor to launch a worker in a resource-segregated container, such as a
> CGroup or Docker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
