You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jose Armando Garcia Sancio (Jira)" <ji...@apache.org> on 2021/05/13 19:54:00 UTC

[jira] [Comment Edited] (KAFKA-10594) Enhance Raft exception handling

    [ https://issues.apache.org/jira/browse/KAFKA-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344032#comment-17344032 ] 

Jose Armando Garcia Sancio edited comment on KAFKA-10594 at 5/13/21, 7:53 PM:
------------------------------------------------------------------------------

I agree with this. There is also an issue that if the {{RaftManager}} thread which polls the {{KafkaRaftClient}} terminates, then the broker or controller JVM process doesn't terminate. I think we need to revisit this.

[~bchen225242] I assume you are not working on this at the moment. I am going to unassigned the issue. Please re-assign it if you are working on this.


was (Author: jagsancio):
I agree with this. There is also an issue that if the RaftManager thread which polls the KafkaRaftClient terminates the broker or controller doesn't terminate. I think need to revisit this.

[~bchen225242] I assume you are not working on this at the moment. I am going to unassigned the issue. Please re-assign it if you are working on this.

> Enhance Raft exception handling
> -------------------------------
>
>                 Key: KAFKA-10594
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10594
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Boyang Chen
>            Priority: Major
>
> The current exception handling on the Raft implementation is superficial, for example we don't treat file system exception and request handling exception differently. It's necessary to decide what kind of exception should be fatal, what kind of exception should be responding to the client, and what exception could be retried.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)