You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/12/22 02:17:00 UTC

[jira] [Resolved] (KAFKA-10842) Refactor raft outbound request channel

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

Jason Gustafson resolved KAFKA-10842.
-------------------------------------
    Resolution: Fixed

> Refactor raft outbound request channel
> --------------------------------------
>
>                 Key: KAFKA-10842
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10842
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>
> There are a few bugs in the current `KafkaNetworkChannel` implementation. Most of the problems are just features which haven't been implemented yet, such as timing out requests which are unable to be sent. Most of these issues are already addressed by `InterBrokerSendThread`. Since this is the class we are standardizing on, we should change the implementation here.
> We also want to address some shortcomings with the current network api used by the raft layer. Specifically we want to allow outbound IO to be done on a separate thread so that it does not block request handling. Additionally, we would like to leave the door more open for concurrent handling of inbound requests, which is not currently possible because all requests (inbound and outbound) are piped through the same `receive()` API.



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