FAQ
After the topology is killed it takes up
to Config.TOPOLOGY_MESSAGE_TIMEOUT_SECS seconds before slots
become available again. During this time bolts keep process pending
messages.
What would be the best way to force kill topology in situations where
timeout is high (like 15 mins, or more)?

ps. Just wondering, how unusual is it to have such a long timeouts? Is
there a way to set timeout per component instead of per topology?

Thanks!

Search Discussions

  • Nathan Marz at Dec 10, 2012 at 8:12 pm
    You can use -w TIME_IN_SECONDS when issuing "storm kill" to override the
    wait time.
    On Thu, Dec 6, 2012 at 4:10 AM, Ivan Balashov wrote:

    After the topology is killed it takes up
    to Config.TOPOLOGY_MESSAGE_TIMEOUT_SECS seconds before slots
    become available again. During this time bolts keep process pending
    messages.
    What would be the best way to force kill topology in situations where
    timeout is high (like 15 mins, or more)?

    ps. Just wondering, how unusual is it to have such a long timeouts? Is
    there a way to set timeout per component instead of per topology?

    Thanks!


    --
    Twitter: @nathanmarz
    http://nathanmarz.com

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupstorm-user @
postedDec 6, '12 at 12:15p
activeDec 10, '12 at 8:12p
posts2
users2
websitestorm-project.net
irc#storm-user

2 users in discussion

Nathan Marz: 1 post Ivan Balashov: 1 post

People

Translate

site design / logo © 2022 Grokbase