You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Dong Lin (JIRA)" <ji...@apache.org> on 2018/10/02 14:46:00 UTC
[jira] [Updated] (KAFKA-6124) Revisit default config for internal
client with regard to resilience
[ https://issues.apache.org/jira/browse/KAFKA-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dong Lin updated KAFKA-6124:
----------------------------
Fix Version/s: (was: 2.1.0)
2.2.0
> Revisit default config for internal client with regard to resilience
> --------------------------------------------------------------------
>
> Key: KAFKA-6124
> URL: https://issues.apache.org/jira/browse/KAFKA-6124
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.0.0
> Reporter: Matthias J. Sax
> Priority: Major
> Labels: needs-kip, streams-resilience
> Fix For: 2.2.0
>
>
> We should reevaluate the default config of our internally used clients, to update them to make Streams more resilient out-of-the-box.
> For example:
> - increase producer "retries"
> - increase producer "max.block.ms"
> - consider impact on max.poll.internal.ms (should we keep it at Integer.MAX_VALUE -- note, that KAFKA-5152 resolve the issue why we did set it to infinity)
> - double check all other defaults including {{KafkaAdmintClient}}
> We should also document all finding in the docs and explain how users can configure their application to be more resilient if they want to.
> This Jira requires a KIP.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)