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/08/06 22:04:00 UTC

[jira] [Updated] (KAFKA-10349) Deprecate client side controller access

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

Boyang Chen updated KAFKA-10349:
--------------------------------
    Description: 
As stated in KIP-590, we would disallow new admin client to discover the controller location for encapsulation. For older broker communication, the metadata response will still contain the controller location.

Note that this should be done as the last step of the redirection changes to ensure all the RPC are migrated and could reach to the controller in new version.

  was:As stated in KIP-590, we would disallow new admin client to discover the controller location for encapsulation. For older broker communication, the metadata response will still contain the controller location.


> Deprecate client side controller access
> ---------------------------------------
>
>                 Key: KAFKA-10349
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10349
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Boyang Chen
>            Priority: Major
>
> As stated in KIP-590, we would disallow new admin client to discover the controller location for encapsulation. For older broker communication, the metadata response will still contain the controller location.
> Note that this should be done as the last step of the redirection changes to ensure all the RPC are migrated and could reach to the controller in new version.



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