You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by devopts <de...@163.com> on 2016/03/14 03:51:13 UTC
Different topologies need different schedulers
Hi all,
I think it is a issue that all topologies only is scheduled by the same scheduler.
And it doesn't work when i set the "storm.scheduler" value in my topology,such as
config.put(Config.STORM_SCHEDULE,xxx.xxx).
Now ,different topologies needs to be scheduled by different schedulers.
And how to solve the problem?
Re: Re: Different topologies need different schedulers
Posted by Bobby Evans <ev...@yahoo-inc.com.INVALID>.
As part of the Resource Aware Scheduler(RAS) we have switch things around to support https://github.com/apache/storm/blob/master/storm-core/src/jvm/org/apache/storm/scheduler/resource/strategies/scheduling/IStrategy.java which can be configured on a per topology basis. - Bobby
On Tuesday, March 15, 2016 3:08 AM, devopts <de...@163.com> wrote:
Hi,
Thank you for your reply.
I think i have solved my issue throgh the java reflection.
Thanks,
devopts
At 2016-03-15 00:55:37, "Li Wang" <wa...@gmail.com> wrote:
>Hi,
>Under current scheduler implementation, I am afraid this can not be achieved. Would you please specify the reason why you want different topologies to be scheduled by different schedulers.
>
>Thanks.
>Li
>
>
>> On 14 Mar 2016, at 10:51 AM, devopts <de...@163.com> wrote:
>>
>> Hi all,
>> I think it is a issue that all topologies only is scheduled by the same scheduler.
>> And it doesn't work when i set the "storm.scheduler" value in my topology,such as
>> config.put(Config.STORM_SCHEDULE,xxx.xxx).
>> Now ,different topologies needs to be scheduled by different schedulers.
>> And how to solve the problem?
>
Re:Re: Different topologies need different schedulers
Posted by devopts <de...@163.com>.
Hi,
Thank you for your reply.
I think i have solved my issue throgh the java reflection.
Thanks,
devopts
At 2016-03-15 00:55:37, "Li Wang" <wa...@gmail.com> wrote:
>Hi,
>Under current scheduler implementation, I am afraid this can not be achieved. Would you please specify the reason why you want different topologies to be scheduled by different schedulers.
>
>Thanks.
>Li
>
>
>> On 14 Mar 2016, at 10:51 AM, devopts <de...@163.com> wrote:
>>
>> Hi all,
>> I think it is a issue that all topologies only is scheduled by the same scheduler.
>> And it doesn't work when i set the "storm.scheduler" value in my topology,such as
>> config.put(Config.STORM_SCHEDULE,xxx.xxx).
>> Now ,different topologies needs to be scheduled by different schedulers.
>> And how to solve the problem?
>
Re: Different topologies need different schedulers
Posted by Li Wang <wa...@gmail.com>.
Hi,
Under current scheduler implementation, I am afraid this can not be achieved. Would you please specify the reason why you want different topologies to be scheduled by different schedulers.
Thanks.
Li
> On 14 Mar 2016, at 10:51 AM, devopts <de...@163.com> wrote:
>
> Hi all,
> I think it is a issue that all topologies only is scheduled by the same scheduler.
> And it doesn't work when i set the "storm.scheduler" value in my topology,such as
> config.put(Config.STORM_SCHEDULE,xxx.xxx).
> Now ,different topologies needs to be scheduled by different schedulers.
> And how to solve the problem?
Re: Different topologies need different schedulers
Posted by "Boyang(Jerry) Peng" <je...@yahoo-inc.com.INVALID>.
This can be solved using the Resource Aware Scheduler. As the resource aware scheduler allows users to specify on a per topology basis what scheduling strategy to use.
On Sunday, March 13, 2016 9:52 PM, devopts <de...@163.com> wrote:
Hi all,
I think it is a issue that all topologies only is scheduled by the same scheduler.
And it doesn't work when i set the "storm.scheduler" value in my topology,such as
config.put(Config.STORM_SCHEDULE,xxx.xxx).
Now ,different topologies needs to be scheduled by different schedulers.
And how to solve the problem?