KAFKA-15831: KIP-1000 protocol and admin client - #14811
Conversation
ce4d98c to
69d55f6
Compare
junrao
left a comment
There was a problem hiding this comment.
@AndrewJSchofield : Thanks for the PR. Just a few minor comments.
| } | ||
|
|
||
| // Just a placeholder for now. | ||
| def handleListClientMetricsResources(request: RequestChannel.Request): CompletableFuture[Unit] = { |
There was a problem hiding this comment.
Why does this return CompletableFuture[Unit] instead of Unit?
There was a problem hiding this comment.
Just giving the option of asynchronous completion. However, since I don't strictly need it now, I am simplifying it to Unit.
| */ | ||
| public KafkaFuture<Collection<ClientMetricsResourceListing>> all() { | ||
| final KafkaFutureImpl<Collection<ClientMetricsResourceListing>> result = new KafkaFutureImpl<>(); | ||
| this.future.whenComplete((listings, throwable) -> { |
| } | ||
|
|
||
| @Test | ||
| public void testListClientMetricsResourcesNotSupported() throws Exception { |
There was a problem hiding this comment.
This method doesn't seem to throw.
There was a problem hiding this comment.
That appears true to me too, but all of the other tests in that source file are the same pattern. I am going for consistency here.
|
Build is almost green. A small number of test failures unrelated to this PR. |
There was a problem hiding this comment.
Thanks for the PR @AndrewJSchofield, LGTM. Minor comments/nit.
junrao
left a comment
There was a problem hiding this comment.
@AndrewJSchofield : Thanks for the updated PR. The code LGTM. Are the 33 test failures related?
|
Also, you could trigger a rerun of the tests by closing the PR, waiting for 20 secs and reopening it. |
|
The test failures are unrelated. I will rerun the tests as requested. |
|
Closing to rerun tests |
|
@AndrewJSchofield : Are the 40 failed tests related? Could you file jiras for failed tests not being tracked yet? |
|
@junrao The failing tests are not related. Here's a summary:
I will file jiras for the 7 failing tests which are not currently being tracked. None of the failures appear related to the code in this PR. |
|
Thanks for the analysis, @AndrewJSchofield. Does the following mean that some of the tests didn't run? Should we rerun the tests? |
|
@AndrewJSchofield : It seems that the last build timed out? |
|
I think so. After 8 hours. I will try resubmitting now (which means it will run overnight for me). In the event that it's still problematic, I'll make a fresh PR and try again. |
|
@junrao This time Java 8, 11 and 21 completed with a handful of unrelated flaky test failures, but Java 17 timed out. The CI system seems to be a dice roll at the moment. |
7c28284 to
00c81f0
Compare
00c81f0 to
b84fc73
Compare
b84fc73 to
c50079e
Compare
|
Just merged a related PR #14767. Re-triggering the tests to make sure there are no new issues. |
junrao
left a comment
There was a problem hiding this comment.
@AndrewJSchofield : Thanks for the PR. The test failures seem unrelated. LGTM
This adds the new ListClientMetricsResources RPC to the Kafka protocol and puts support into the Kafka admin client. The broker-side implementation in this PR is just to return an empty list. A future PR will obtain the list from the config store. Includes a few unit tests for what is a very simple RPC. There are additional tests already written and waiting for the PR that delivers the kafka-client-metrics.sh tool which builds on this PR. Reviewers: Jun Rao <junrao@gmail.com>
This adds the new ListClientMetricsResources RPC to the Kafka protocol and puts support into the Kafka admin client. The broker-side implementation in this PR is just to return an empty list. A future PR will obtain the list from the config store. Includes a few unit tests for what is a very simple RPC. There are additional tests already written and waiting for the PR that delivers the kafka-client-metrics.sh tool which builds on this PR. Reviewers: Jun Rao <junrao@gmail.com>
This adds the new ListClientMetricsResources RPC to the Kafka protocol and puts support into the Kafka admin client. The broker-side implementation in this PR is just to return an empty list. A future PR will obtain the list from the config store. Includes a few unit tests for what is a very simple RPC. There are additional tests already written and waiting for the PR that delivers the kafka-client-metrics.sh tool which builds on this PR. Reviewers: Jun Rao <junrao@gmail.com>
This adds the new ListClientMetricsResources RPC to the Kafka protocol and puts support into the Kafka admin client. The broker-side implementation in this PR is just to return an empty list. A future PR will obtain the list from the config store. Includes a few unit tests for what is a very simple RPC. There are additional tests already written and waiting for the PR that delivers the kafka-client-metrics.sh tool which builds on this PR. Reviewers: Jun Rao <junrao@gmail.com>
This adds the new ListClientMetricsResources RPC to the Kafka protocol and puts support
into the Kafka admin client. The broker-side implementation in this PR is just to return an empty
list. A future PR will obtain the list from the config store.
Includes a few unit tests for what is a very simple RPC. There are additional tests already written and
waiting for the PR that delivers the
kafka-client-metrics.shtool which builds on this PR.Committer Checklist (excluded from commit message)