You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "Satish Duggana (JIRA)" <ji...@apache.org> on 2016/06/30 12:40:10 UTC

[jira] [Updated] (STORM-1938) Nimbus 's mk-assignments scheduler should act immediately whenever there are topology related tasks are submitted.

     [ https://issues.apache.org/jira/browse/STORM-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Satish Duggana updated STORM-1938:
----------------------------------
    Description: Currently, nimbus’s mk-assignments task runs at configured `nimbus.monitor.freq.secs`scheduled intervals. Sometimes, this causes the pending topology related tasks to wait till next scheduled interval. This can be improved not to wait for next scheduled interval but as and when there are tasks submitted. This behavior can be based on a configuration to maintain backward compatibility. It gives flexibility not to read from zk when there are topology related tasks but at configured intervals.  (was: Currently, nimbus’s mk-assignments task runs at configured ``scheduled intervals. Sometimes, this causes the pending topology related tasks to wait till next scheduled interval. This can be improved not to wait for next scheduled interval but as and when there are tasks submitted. This behavior can be based on a configuration to maintain backward compatibility. It gives flexibility not to read from zk when there are topology related tasks but at configured intervals.)

> Nimbus 's mk-assignments scheduler should act immediately whenever there are topology related tasks are submitted.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: STORM-1938
>                 URL: https://issues.apache.org/jira/browse/STORM-1938
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Satish Duggana
>            Assignee: Satish Duggana
>            Priority: Critical
>
> Currently, nimbus’s mk-assignments task runs at configured `nimbus.monitor.freq.secs`scheduled intervals. Sometimes, this causes the pending topology related tasks to wait till next scheduled interval. This can be improved not to wait for next scheduled interval but as and when there are tasks submitted. This behavior can be based on a configuration to maintain backward compatibility. It gives flexibility not to read from zk when there are topology related tasks but at configured intervals.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)