-
Type:
Build Failure
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing
-
None
-
None
-
Go Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Name of Failure:
timed out while checking out a connection from connection pool: context deadline exceeded; total connections: 0, maxPoolSize: 100, idle connections: 0, wait duration: 1.737µs
Link to task:
Context of when and why the failure occurred:
There is a server bug (SERVER-129623) caused by delaying the first empty batch from aggregating by periodicNoopIntervalSecs (DET orchestration sets this to 1s). The CSOT failures are coincidental and can be resolved by updating the timeoutMS to 1020, or some value > 1s.
Stack trace:
Unnecessary
Definition of Done
- Skip affected tests until resolution of SERVER-129623 for sharded clusters on server versions >= 9.0
- Advance cluster time in integration tests that rely on setting deadlines < 1s for Watch for sharded clusters
- Create follow-up GODRIVER ticket to track
- is fixed by
-
GODRIVER-4011 Skip time-sensitive CSOT tests opening change streams on 9.0+ sharded clusters
-
- Investigating
-
There are no Sub-Tasks for this issue.