[GODRIVER-1799] Avoiding connection storms Created: 18/Nov/20  Updated: 28/Oct/23  Resolved: 22/Mar/22

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 1.9.0

Type: Epic Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Matt Dale
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
Related
related to GODRIVER-1885 Client Side Operations Timeout Closed
related to GODRIVER-2065 Error early if insufficient time rema... Closed
related to GODRIVER-2038 Use "ConnectionTimeout" for creating ... Closed
Quarter: FY22Q4
Start date:
End date:
Calendar Time: 15 weeks
Scope Cost Estimate: 8
Cost to Date: 9
Final Cost Estimate: 10
Cost Threshold %: 100
Detailed Project Statuses:

Engineer(s): Matt

2022-03-07: Updated target end date to 2022-03-18

Status update:

  • Completed connection pool pausing.
  • Updates to resync maxConnecting related tests in review.
  • Consider server load during server selection is scheduled.

Rationale for delays:

  • Connection pool pausing was more complex than expected.
  • Go driver connection pool behavior differs from most other drivers. The Go driver establishes all connections in a background goroutines (part of GODRIVER-2038). This resulted in three CMAP tests not being able to work with the Go driver. Drivers tickets were filed.

Risks:

  • No risks.

2022-02-21: Updating target date to 2022-03-01.

Status update:

  • Connection pool pausing in review.
    • Met to discuss PR. 1 of 3 reviewers have approved.
    • Resolved an intermittent test failure.

Rationale for delays:

  • Reviews have been slower. Team busy on hiring and responding to questions in #go-driver.
  • Discovered an intermittent test failure during PR.

Risks:

  • No risks.

2022-02-07: Updated target end date to 2022-02-18

Status update:

  • Connection pool pausing in review.

Rationale for delays:

  • Connection pool pausing implementation was unexpectedly challenging. Required refactor of operation layer to permit retry of connection pool checkout.

Risks:

  • No risks.

2022-01-25: No change to target date

Status update:

  • Focus is on implementing pausable state for pool, which will unblock many spec tests.

Rationale for delays:

  • No delays.

Risks:

  • No risks.

2022-01-11: No change to target date

Status update:

  • PR for prose-style tests for the maxConnecting CMAP spec approved. Fixing test failures.
  • Configurable maxConnecting released in 1.8.2.

Rationale for delays:

  • No delays.

Risks:

  • No risks.

---- 

2021-12-27: No change to target date.

Status update:

  • PR for prose-style tests for the maxConnecting CMAP spec.
  • Spec tests were not possible to run in Go driver since it relied on private API unavailable to integration test runner.

Rationale for delays:

  • No delays.

Risks:

  • No risks.

2021-12-13:

Status update:

  • Working on maxConnecting and rate limiting.

Rationale for delays:

  • No delays.

Risks:

  • No risks.


 Description   

See DRIVERS-781 for updated details.



 Comments   
Comment by PM Bot [ 25/Jan/22 ]

If you are not logged in, you can view the tickets in this epic by following this link.

Comment by PM Bot [ 11/Jan/22 ]

If you are not logged in, you can view the tickets in this epic by following this link.

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