dengziming
dengziming
*More detailed description of your change* The reason for KAFKA-13959 is a little complex, the two keys to this problem are: 1. `KafkaRaftClient.MAX_FETCH_WAIT_MS==MetadataMaxIdleIntervalMs == 500ms`. We rely on fetchPurgatory to...
*More detailed description of your change, if necessary. The PR title and PR message become the squashed commit message, so use a separate comment to ping reviewers.* Add `MetadataQuorumCommand` to...
*More detailed description of your change* Currently, 8 record types are missing in MetadataShell: 1. AccessControlEntryRecord and RemoveAccessControlEntryRecord are added in KIP-801, FeatureLevelRecord and maybe RemoveFeatureLevelRecord will be added in...
*More detailed description of your change, if necessary. The PR title and PR message become the squashed commit message, so use a separate comment to ping reviewers.* Support --release in...
*More detailed description of your change* Updating metadata.version using AdminClient will fail with the following exception: ``` java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidUpdateVersionException: Invalid update version 7 for feature metadata.version. Controller 3000 does not...
*More detailed description of your change* Support kraft mode in RequestQuotaTest *Summary of testing strategy (including rationale)* QA ### Committer Checklist (excluded from commit message) - [ ] Verify design...
*More detailed description of your change, if necessary. The PR title and PR message become the squashed commit message, so use a separate comment to ping reviewers.* We have Admin.updateFeatures(Map,...
*More detailed description of your change* This PR implement KIP-1011, use incrementalAlterConfigs by default to alter broker configurations instead of the deprecated alterConfigs API, and fall back to deprecated alterConfigs...