Page History

...

• AlterConfig

• IncrementalAlterConfig 

• CreateAcls

• DeleteAcls

• AlterClientQuotas

• CreateDelegationToken

• RenewDelegationToken 

• ExpireDelegationToken

...

Internal CreateTopicsRequest Routing 

One Certain edge case cases we would also like to fix is for the internal topic creation.

1. FindCoordinator protocol

...

1. has

...

1. an internal topic creation logic when the cluster receives the request for the first time as transaction log topic and consumer offset topic are lazily initialized. 
2. MetadataRequest protocol also contains an internal topic creation logic when we are looking for metadata for a non-existing internal topic and auto-topic-creation is enabled.

Currently the target broker shall just utilize its own ZK client to create topicinternal topics, which is disallowed in the bridge release. For this scenarioabove scenarios, non-controller broker shall just forward a CreateTopicRequest to the controller instead and let controller take care of the rest, while waiting for the response in the mean time. 

Routing Request Security

For older requests that need redirection, forwarding broker will just use its own authorizer to verify the principals. When the request looks good, it will just forward the request with its own credentials, no second validation needed. The only exceptional case is the controller audit log which needs a principal name of the request, so we will add an optional tag called "PrincipalName" to the header when sending the proxy request.

...

• AlterConfig to v2

• IncrementalAlterConfig to v2

• CreateAcls to v3

• DeleteAcls to v3

• AlterClientQuotas to v1

• CreateDelegationToken to v3

• RenewDelegationToken to v3

• ExpireDelegationToken to v3

The FindCoordinator CreateTopic routing change is purely inter-broker, and . Since the CreateTopicRequest is already handled by controller only, so no change for bothon this side.

New Tag for Principal Name

...