Table of Contents |
---|
Status
Current state: Under DiscussionAdopted
Discussion thread: here
JIRA:
(0.10.2.0) Jira server ASF JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-4565
(0.11.0.0) Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-4636
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
Code Block | ||
---|---|---|
| ||
{ "version": 4, "jmx_port": 9999, "timestamp": 2233345666, "host": "localhost", "port": 9092, "rack": "rack1", "listener._security._protocol._map": { "PLAINTEXT": "PLAINTEXT", "SSL": "SSL", "SASL_PLAINTEXT": "SASL_PLAINTEXT", "SASL_SSL": "SASL_SSL" }, "endpoints": [ "CLIENT://cluster1.foo.com:9092", "REPLICATION: //broker1.replication.local:9093", "INTERNAL_PLAINTEXT: //broker1.local:9094", "INTERNAL_SASL://broker1.local:9095" ] } |
Protocol
Version 2 3 of UpdateMetadataRequest
will be introduced and the elements of the end_points
array would also have a listener_name field.
Code Block |
---|
UpdateMetadata Request (Version: 23) => controller_id controller_epoch [partition_states] [live_brokers] controller_id => INT32 controller_epoch => INT32 partition_states => topic partition controller_epoch leader leader_epoch [isr] zk_version [replicas] topic => STRING partition => INT32 controller_epoch => INT32 leader => INT32 leader_epoch => INT32 isr => INT32 zk_version => INT32 replicas => INT32 live_brokers => id [end_points] id => INT32 end_points => port host listener_name (new) security_protocol_type port => INT32 host => STRING listener_name => String (new) security_protocol_type => INT16 |
...