[STORM-3335] timeout when scheduling topology runs too long

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Labels: pull-request-available
• Assignee: Aaron Gresch
• Reporter: Aaron Gresch
• Created: 08/Feb/19 21:51
• Updated: 21/Feb/19 10:36
• Resolved: 21/Feb/19 10:36

Description

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. 

Issue Links

• links to: GitHub Pull Request #2957