[JAVA-4883] Test failing fairly consistently on 4.0 sharded clusters Created: 16/Feb/23  Updated: 28/Oct/23  Resolved: 09/Mar/23

Status: Closed
Project: Java Driver
Component/s: Test Failure
Affects Version/s: None
Fix Version/s: 4.10.0

Type: Improvement Priority: Unknown
Reporter: Jeffrey Yemin Assignee: Jeffrey Yemin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Documentation Changes: Not Needed
Documentation Changes Summary:

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?


 Description   

Example: https://evergreen.mongodb.com/task_history/mongo-java-driver/test?revision=bc05e539c91f07fdd42aef71c9247478d0fb5808#com.mongodb.client.WriteConcernOperationTest.shouldPassAllOutcomes_default-write-concern-3.4.json__Aggregate_with__out_omits_default_write_concern_=fail

Since it's 4.0 only, consider just skipping the test there, though that may just move the failure.



 Comments   
Comment by Githook User [ 09/Mar/23 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Work around create failure in unified tests with retry (#1094)

On 4.0 sharded clusters, the create collection command often fails
with error code 11601 (Interrupted). Work around it by retrying
the command.

JAVA-4883
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/582356c3d8c1d700f5a89f6226821ec7f47983c8

Generated at Thu Feb 08 09:03:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.