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

Posted to issues@storm.apache.org by "Ethan Li (Jira)" <ji...@apache.org> on 2019/08/22 16:31:00 UTC

[jira] [Commented] (STORM-3492) Adding configuration for blacklisting scheduler behavior

    [ https://issues.apache.org/jira/browse/STORM-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913477#comment-16913477 ] 

Ethan Li commented on STORM-3492:
---------------------------------

Please create a follow-up jira to add unit tests for this feature. Thank you

> Adding configuration for blacklisting scheduler behavior
> --------------------------------------------------------
>
>                 Key: STORM-3492
>                 URL: https://issues.apache.org/jira/browse/STORM-3492
>             Project: Apache Storm
>          Issue Type: New Feature
>            Reporter: Rui Li
>            Assignee: Rui Li
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.2.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Recently, we have experience situations where supervisor kept restarting workers when some problematic topologies were submitted. This will cause supervisor get blacklisted even if the supervisor is good.
> Some large topologies may causes a significant part of nodes to blacklist. 
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)