Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First draft of system tests for the new share consumer client #18209

Draft
wants to merge 2 commits into
base: trunk
Choose a base branch
from

Conversation

chirag-wadhwa5
Copy link
Contributor

This is the first draft for System Tests for the new share consumer client introduced as part of KIP-932

@github-actions github-actions bot added triage PRs from the community tools labels Dec 16, 2024
Copy link
Member

@AndrewJSchofield AndrewJSchofield left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this draft PR. I'll take a proper look and try running it myself. It's good to see progress on the system tests.

@@ -288,6 +288,8 @@
files="VerifiableConsumer.java"/>
<suppress id="dontUseSystemExit"
files="VerifiableProducer.java"/>
<suppress id="dontUseSystemExit"
files="VerifiableShareGroup.java"/>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VerifiableShareGroup doesn't exist. Do you mean VerifiableShareConsumer?

@@ -142,10 +142,10 @@
def create_verifiable_client_implementation(context, parent):
"""Factory for generating a verifiable client implementation class instance

:param parent: parent class instance, either VerifiableConsumer or VerifiableProducer
:param parent: parent class instance, either VerifiableConsumer, VerifiableProducer or VerifiableShareGroup
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These references to VerifiableShareGroup and ShareGroup should probably be VerifiableShareConsumer and ShareConsumer.

@AndrewJSchofield AndrewJSchofield added KIP-932 Queues for Kafka and removed triage PRs from the community labels Dec 16, 2024
Copy link
Member

@AndrewJSchofield AndrewJSchofield left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some more comments. Overall, the approach of the verifiable share consumer seems like a good starting point. There are too many files specific to running locally in this PR at the moment I think.


private static ArgumentParser argParser() {
ArgumentParser parser = ArgumentParsers
.newArgumentParser("verifiable-share-group")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"verifiable-share-consumer"

.setDefault("")
.type(String.class)
.dest("offsetResetStrategy")
.help("Set share group reset strategy (must be either 'earliest' or 'latest'");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Missing ')' int he string.

}
}
} catch (WakeupException e) {
out.println("caught wakeup exception: " + e);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line please.

// ignore, we are closing
log.trace("Caught WakeupException because share consumer is shutdown, ignore and terminate.", e);
} catch (Throwable t) {
out.println("caught throwable exception: " + t);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And this one.

printJson(new RecordData(record));
}
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Extraneous line.

// Log the error, so it goes to the service log and not stdout
log.error("Error during processing, terminating share consumer process: ", t);
} finally {
out.println("Total records Consumed: " + totalConsumed.toString());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want to write out these pieces of information, I suggest a better way is appropriate. I'd remove these two printlns.

private final boolean success;

public OffsetsAcknowledged(long count, List<AcknowledgedData> partitions, String error, boolean success) {
this.count=count;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: spacing

@@ -0,0 +1,35 @@
#!/bin/bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file seems like a script you could use locally to run using docker. I don't think it should be part of a PR.

@@ -126,3 +126,11 @@ offsets.topic.num.partitions={{ num_nodes }}
offsets.topic.replication.factor={{ 3 if num_nodes > 3 else num_nodes }}
# Set to a low, but non-zero value to exercise this path without making tests much slower
group.initial.rebalance.delay.ms=100

group.coordinator.rebalance.protocols=classic,consumer,share
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There needs to be a better way to manage the configs here. Changing this file changes the configs for all of the tests, and that doesn't seem right when KIP-932 is still in early access. I think you should not include this change in the PR.

from kafkatest.directory_layout.kafka_path import KafkaPathResolverMixin
from kafkatest.services.kafka import TopicPartition
from kafkatest.services.verifiable_client import VerifiableClientMixin
from kafkatest.version import DEV_BRANCH, V_2_3_0, V_2_3_1, V_3_7_0, V_4_0_0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be applicable for DEV_BRANCH and V_4_1_0 only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
KIP-932 Queues for Kafka tools
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants