You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Derek Dagit (JIRA)" <ji...@apache.org> on 2018/11/09 16:13:00 UTC

[jira] [Updated] (STORM-3285) A way to disable/enable nimbus rescheduling assignments

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

Derek Dagit updated STORM-3285:
-------------------------------
    Summary: A way to disable/enable nimbus rescheduling assignments  (was: A way to disable/enable nimbus rescheduling)

> A way to disable/enable nimbus rescheduling assignments
> -------------------------------------------------------
>
>                 Key: STORM-3285
>                 URL: https://issues.apache.org/jira/browse/STORM-3285
>             Project: Apache Storm
>          Issue Type: New Feature
>          Components: storm-core
>            Reporter: Derek Dagit
>            Priority: Minor
>
> As an Apache Storm administrator, I would like to be able to skip topology assignment updates without stopping the nimbus daemon, so that I can debug issues with the cluster in a more stable situation.
> In scenarios where supervisor black-listing is active, topology workers can be reassigned away from supervisor hosts more frequently than desired for debugging.
> While it is possible to disable changes to topology assignments by stopping nimbus, this has the effect of disable other services, such as the UI.
> It would be nice to have some way to "deactivate" the assignment changes while letting everything else—including the scheduling logic—to run as normal. This could be done with a reload-able config, a special "kill file" whose presence tells nimbus to skip, or some control instruction via the API (e.g., {{storm admin suspend-assignments <TIMEOUT-SECONDS>}}).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)