You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/07/18 16:25:00 UTC

[jira] [Reopened] (KAFKA-5302) Improve exception handling on streams client (communication with brokers)

     [ https://issues.apache.org/jira/browse/KAFKA-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guozhang Wang reopened KAFKA-5302:
----------------------------------

[~enothereska] Let's leave this ticket open until we have done the migration; also we can use this JIRA as a reference for the current known issues with the streams client and make sure these are appropriately handled when we replace with the admin client.

> Improve exception handling on streams client (communication with brokers)
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-5302
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5302
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>    Affects Versions: 0.11.0.0
>            Reporter: Eno Thereska
>            Assignee: Eno Thereska
>             Fix For: 0.11.1.0
>
>
> These are exceptions in StreamsKafkaClient.java.
> Currently throws either StreamsException or BrokerNotFoundException.
> Used by InternalTopicManager to create topics and get their metadata.
> Used by StreamPartitionAssignor. 
> Currently InternalTopicManager retries a few times after catching an exception. 
> A failure here is sent all the way up to the stream thread and will stop the streams pipeline. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)