Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

After this process, all servers will be aware of the latest set of internal topics and can cache internal topics in MedatadaCache. Thus, that KafkaApi can construct the metadata response with the information of all clients created internal topics by referring MetadataCache. 

...

Internal topic behaviors

Below will be the Kafka allowed operations for internal topics. However, Cluster admins might want to control the operations on internal topics using ACLs as they might be dangerous.

  1. Internal topic creation will be allowed.
  2. Internal topic deletion will be allowed except for` __consumer_offsets` and `__transaction_state`.
  3. Producing to internal topic partitions other than `__consumer_offsets` and `__transaction_state` will be allowed.
  4. Adding internal topics to transactions will be allowed.

Post ZK world

KIP-500 proposed metadata quorum. Since the changes proposed in this KIP interact directly with KafkaApi instead of Zookeeper and modifies the cached metadata, it should be easily migrated in Post ZK world.

Client-side:

To get the internal topic information, instead of using the static internal topic testing or implementing their own logic, clients can utilize KafkaAdminClients and make a MetadataRequest (ApiKey.METADATA). 

...