You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Boyang Chen (Jira)" <ji...@apache.org> on 2020/10/30 21:24:00 UTC

[jira] [Updated] (KAFKA-10668) Avoid deserialization on second hop for request forwarding

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

Boyang Chen updated KAFKA-10668:
--------------------------------
    Description: 
Right now on forwarding broker we would deserialize the response and serialize it again to respond to the client. It should be able to keep the response data sealed and send back to the client to save some CPU cost.

Original comment: https://github.com/apache/kafka/pull/9103#discussion_r515219726

  was:Right now on forwarding broker we would deserialize the response and serialize it again to respond to the client. It should be able to keep the response data sealed and send back to the client to save some CPU cost.


> Avoid deserialization on second hop for request forwarding
> ----------------------------------------------------------
>
>                 Key: KAFKA-10668
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10668
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Boyang Chen
>            Priority: Major
>
> Right now on forwarding broker we would deserialize the response and serialize it again to respond to the client. It should be able to keep the response data sealed and send back to the client to save some CPU cost.
> Original comment: https://github.com/apache/kafka/pull/9103#discussion_r515219726



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