[LI-HOTFIX] Add test case for describe maintenance broker config - #248
Merged
lmr3796 merged 3 commits intoJan 18, 2022
Merged
Conversation
TICKET = KAFKA-8527 LI_DESCRIPTION = In the commit 6b93c27 `[LI-HOTFIX] Add dynamic maintenance broker config`, the test cases didn't cover the describe config API. Adding this to protect the code path and facilitate the future rebase process. EXIT_CRITERIA = TICKET [KAFKA-8527] or the patch is dropped
lmr3796
force-pushed
the
describe-maintenance-broker-config
branch
from
January 18, 2022 18:34
5f42b13 to
8b2520d
Compare
wyuka
approved these changes
Jan 18, 2022
lmr3796
pushed a commit
to lmr3796/kafka
that referenced
this pull request
Jan 18, 2022
This also squashes the directly related test commits - e59b0da [LI-HOTFIX] Add test case for describe maintenance broker config (linkedin#248) - 1f7bab6 [LI-HOTFIX] fix DynamicConfig and DynamicBrokerConfig cross reference issue (linkedin#69) TICKET = KAFKA-8527 LI_DESCRIPTION = When a broker is masked as maintenance broker, Kafka will not assign partitions of new topics to the broker if partition assignment is done by kafka brokers. 1) add dynamic broker config to support maintenance brokers 2) add logic to update maintenance broker info in controller 3) support maintenance broker in Kafka API 4) support maintenance broker in AdminZkClient 5) add logic to rearrange replica assignment for new topics for maintenance brokers 5) test cases RB=1484649 G=Kafka-Code-Reviews R=agencer, amendhek, jkoshy, zahuang A=zahuang EXIT_CRITERIA = TICKET [KAFKA-8527]
lmr3796
pushed a commit
to lmr3796/kafka
that referenced
this pull request
Feb 9, 2022
This also squashes the directly related test commits - e59b0da [LI-HOTFIX] Add test case for describe maintenance broker config (linkedin#248) - 1f7bab6 [LI-HOTFIX] fix DynamicConfig and DynamicBrokerConfig cross reference issue (linkedin#69) TICKET = KAFKA-8527 LI_DESCRIPTION = When a broker is masked as maintenance broker, Kafka will not assign partitions of new topics to the broker if partition assignment is done by kafka brokers. 1) add dynamic broker config to support maintenance brokers 2) add logic to update maintenance broker info in controller 3) support maintenance broker in Kafka API 4) support maintenance broker in AdminZkClient 5) add logic to rearrange replica assignment for new topics for maintenance brokers 5) test cases RB=1484649 G=Kafka-Code-Reviews R=agencer, amendhek, jkoshy, zahuang A=zahuang EXIT_CRITERIA = TICKET [KAFKA-8527]
lmr3796
pushed a commit
to lmr3796/kafka
that referenced
this pull request
Mar 25, 2022
This also squashes the directly related test commits - e59b0da [LI-HOTFIX] Add test case for describe maintenance broker config (linkedin#248) - 1f7bab6 [LI-HOTFIX] fix DynamicConfig and DynamicBrokerConfig cross reference issue (linkedin#69) TICKET = KAFKA-8527 LI_DESCRIPTION = When a broker is masked as maintenance broker, Kafka will not assign partitions of new topics to the broker if partition assignment is done by kafka brokers. 1) add dynamic broker config to support maintenance brokers 2) add logic to update maintenance broker info in controller 3) support maintenance broker in Kafka API 4) support maintenance broker in AdminZkClient 5) add logic to rearrange replica assignment for new topics for maintenance brokers 5) test cases RB=1484649 G=Kafka-Code-Reviews R=agencer, amendhek, jkoshy, zahuang A=zahuang EXIT_CRITERIA = TICKET [KAFKA-8527]
lmr3796
pushed a commit
to lmr3796/kafka
that referenced
this pull request
Jun 2, 2022
This also squashes the directly related test commits - e59b0da [LI-HOTFIX] Add test case for describe maintenance broker config (linkedin#248) - 1f7bab6 [LI-HOTFIX] fix DynamicConfig and DynamicBrokerConfig cross reference issue (linkedin#69) TICKET = KAFKA-8527 LI_DESCRIPTION = When a broker is masked as maintenance broker, Kafka will not assign partitions of new topics to the broker if partition assignment is done by kafka brokers. 1) add dynamic broker config to support maintenance brokers 2) add logic to update maintenance broker info in controller 3) support maintenance broker in Kafka API 4) support maintenance broker in AdminZkClient 5) add logic to rearrange replica assignment for new topics for maintenance brokers 5) test cases RB=1484649 G=Kafka-Code-Reviews R=agencer, amendhek, jkoshy, zahuang A=zahuang EXIT_CRITERIA = TICKET [KAFKA-8527]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TICKET = KAFKA-8527
LI_DESCRIPTION =
In the commit 6b93c27
[LI-HOTFIX] Add dynamic maintenance broker config, the test cases didn't cover the describe config API.Adding this to protect the code path and facilitate the future rebase process.
EXIT_CRITERIA = TICKET [KAFKA-8527] or the patch is dropped
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.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)