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

Fix flaky Key_Shared subscription related tests #970

Merged

Conversation

BewareMyPower
Copy link
Contributor

Motivation

After #953, the Pulsar version was upgraded from 2.8.3 to 2.10.3. However, PIP-119 changed the default value of subscriptionKeySharedUseConsistentHashing to true, which leads to the flakiness of Key_Shared subscription related tests.

Example: https://github.com/apache/pulsar-client-go/actions/runs/4291098473/jobs/7475868787

Modifications

Configure subscriptionKeySharedUseConsistentHashing with false.

### Motivation

After apache#953, the Pulsar
version was upgraded from 2.8.3 to 2.10.3. However,
[PIP-119](apache/pulsar#13352) changed the
default value of `subscriptionKeySharedUseConsistentHashing` to true,
which leads to the flakiness of Key_Shared subscription related tests.

Example: https://github.com/apache/pulsar-client-go/actions/runs/4291098473/jobs/7475868787

### Modifications

Configure `subscriptionKeySharedUseConsistentHashing` with `false`.
@BewareMyPower
Copy link
Contributor Author

It looks like TestConsumerBatchCumulativeAck is flaky, and I will rerun it first.

@BewareMyPower
Copy link
Contributor Author

The flaky TestConsumerBatchCumulativeAck is caused by the timeout of client.Close(). The "request timed out" happened when there are some pending responses while closing. I have encountered this issue very often when I ran a performance test locally and press Ctrl+C to stop. I will try to fix it later.

@BewareMyPower
Copy link
Contributor Author

Another flaky test: #971

@shibd shibd merged commit d60bff6 into apache:master Mar 1, 2023
@BewareMyPower BewareMyPower deleted the bewaremypower/fix-flaky-key-shared branch March 1, 2023 02:11
@RobertIndie RobertIndie added this to the v0.10.0 milestone Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants