Rick Kilgore created STORM-495:
----------------------------------
Summary: Add delayed retries to KafkaSpout
Key: STORM-495
URL: https://issues.apache.org/jira/browse/STORM-495
Project: Apache Storm (Incubating)
Issue Type: Improvement
Affects Versions: 0.9.3-incubating
Environment: all environments
Reporter: Rick Kilgore
Priority: Minor
If a tuple in the topology originates from the KafkaSpout from the
external/storm-kafka sources, and if a bolt in the topology indicates a failure
by calling fail() on its OutputCollector, the KafkaSpout will immediately retry
the message.
We wish to use this failure and retry behavior in our ingestion system whenever
we experience a recoverable error from a downstream system, such as a 500 or
503 error from a service we depend on. But with the current KafkaSpout
behavior, doing so results in a tight loop where we retry several times over a
few seconds and then give up. I want to be able to delay retry to give the
downstream service some time to recover. Ideally, I would like to have
configurable, exponential backoff retry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
