Storm: you can set topology.message.timeout.secs much higher for a single bolt

Question

Part of my topology depends on working with a third-party API, which restricts certain calls to 15-minute windows. In the worst case, the speed limit will land and the bolt will have to sleep for 15 minutes. Unfortunately, it seems that I can’t say that the storm “sleeps” on the task for 15 minutes, but I hope I'm wrong.

Alternatively, is there a way to handle a time-limited task like this in a storm? (do you have a nose with another nose?).

Answer 1

I am not aware of any configuration that allows this, and Config does not offer a configuration entry for it.

Workaround as you suggested. When you got your output from a third-party API, submit it to a special nozzle, which, in turn, issues it to the “callback” Bolt.

Answer 2

You can take a look at ticktuple (but this is only 600 seconds)

 ``` Config conf = new Config(); conf.put(Config.TOPOLOGY_TICK_TUPLE_FREQ_SECS, 1); ``` 

So look this

Answer 3

You might want to check the TOPOLOGY_DISRUPTOR_WAIT_STRATEGY attribute as indicated here