You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2017/10/25 23:14:00 UTC

[jira] [Resolved] (KAFKA-5313) Improve exception handling on coordinator interactions

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

Matthias J. Sax resolved KAFKA-5313.
------------------------------------
    Resolution: Duplicate

This is contained by all other exception handling tasks of this umbrella, thus I am closing as duplicate.

> Improve exception handling on coordinator interactions
> ------------------------------------------------------
>
>                 Key: KAFKA-5313
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5313
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>    Affects Versions: 0.11.0.0
>            Reporter: Eno Thereska
>            Assignee: Matthias J. Sax
>             Fix For: 1.1.0
>
>
> Exceptions during assignment of tasks are caught in ConsumerCoordinator.java and streams becomes aware of them during the StreamThread.onPartitionsAssigned() and StreamThread.onPartitionsRevoked() methods. Eventually these exceptions go through StreamThread.pollRequests() all the way up to StreamThread.runLoop() and will halt the stream thread that is processing these exceptions. Other stream threads may continue processing, however it is likely they will experience problems too soon after.
> Exceptions here include LockExceptions that are thrown if tasks cannot use a particular directory due to previous tasks not releasing locks on them during reassignment. 



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