[
https://issues.apache.org/jira/browse/KAFKA-12711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331098#comment-17331098
]
Guozhang Wang commented on KAFKA-12711:
---------------------------------------
On the other hand, I think maybe we do not, at least in the first attempt, need
to expose backoff to users to customize: we can consider just hard-code an
exponential backoff mechanism inside Streams (we can pick some magic numbers
here) to begin with, and hence no need for a KIP.
> Add a back off option to replace thread
> ---------------------------------------
>
> Key: KAFKA-12711
> URL: https://issues.apache.org/jira/browse/KAFKA-12711
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Walker Carlson
> Priority: Major
> Labels: needs-kip
>
> There should be a native option to set a back off period when replacing a
> thread from the stream uncaught exception handler.
>
> Either there should be a config and a user chosen strategy or a value you can
> set in the handler that causes a delay in creating the new thread.
>
> It might also be achieved by making the option to add a thread in N seconds
> then using that in the replace thread option
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
