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

Posted to issues@storm.apache.org by "Stig Rohde Døssing (JIRA)" <ji...@apache.org> on 2019/02/21 10:37:01 UTC

[jira] [Resolved] (STORM-3335) timeout when scheduling topology runs too long

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

Stig Rohde Døssing resolved STORM-3335.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Thanks [~agresch], merged to master

> timeout when scheduling topology runs too long
> ----------------------------------------------
>
>                 Key: STORM-3335
>                 URL: https://issues.apache.org/jira/browse/STORM-3335
>             Project: Apache Storm
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Aaron Gresch
>            Assignee: Aaron Gresch
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> We encountered an issue where a user submitted a topology and after a few minutes tried to kill it and failed.  After debugging we found that scheduling was running for topology for at least 30 minutes, causing the kill to be backlogged on the timer task. 



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