[JAVA-4259] Fix LB-related bugs in AsyncQueryBatchCursor that cause test failures Created: 24/Jul/21  Updated: 30/Mar/22

Status: Backlog
Project: Java Driver
Component/s: Reactive Streams, Test Coverage
Affects Version/s: 4.3.0
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Valentin Kavalenka Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before JAVA-4260 AsyncQueryBatchCursor should not try ... Backlog
Issue split
split from JAVA-4183 Calling cursor.next() and cursor.clos... Closed
Epic Link: Investigate flaky tests

 Description   

While working on JAVA-4183, I discovered that some integration tests for AsyncQueryBatchCursor fail when run with load balancer, and one spec test seems to fail sporadically and quite rarely. There is a good chance that these failures all have the same cause. These failures prevented me from running AsyncQueryBatchCursorFunctionalSpecification together with QueryBatchCursorFunctionalSpecification with load balancer (the latter runs with load balancer since JAVA-4183).

Both of the above patches are done by using https://github.com/mongodb/mongo-java-driver/pull/765 as the base (note that this PR does touches neither AsyncQueryBatchCursor nor AsyncQueryBatchCursorFunctionalSpecification), removing @Slow annotations from tests (because of JAVA-4145) in AsyncQueryBatchCursorFunctionalSpecification and adding these tests to run-load-balancer-tests.sh. I was not able to do this with master because the aforementioned PR has changes needed to support running AsyncQueryBatchCursorFunctionalSpecification with load balancer. By the time this ticket is in progress, the aforementioned PR will probably have been merged, and the experiment may be repeated with master.

Implementation of this ticket should also add AsyncQueryBatchCursorFunctionalSpecification to run-load-balancer-tests.sh.


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