[SERVER-39168] Prototype Better Predictive Connection Pool Sizing Created: 24/Jan/19  Updated: 01/Mar/19  Resolved: 01/Mar/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Benjamin Caimano (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-38920 Allow ShardingTaskExecutorPool parame... Closed
Sprint: Service Arch 2019-01-28, Service Arch 2019-02-11, Service Arch 2019-02-25, Service Arch 2019-03-11
Participants:

 Description   

It seems like design decisions will be much more informed if there is an initial prototype.



 Comments   
Comment by Benjamin Caimano (Inactive) [ 01/Mar/19 ]

I've managed to get a reasonable hacked version of this. I've got it going here. I'll be pulling off and cleaning up pieces of it to land.

Comment by Benjamin Caimano (Inactive) [ 21/Feb/19 ]

Here are my proposed tickets from this:

  • Expand ConnectionPool::Options to take in all ctor params
  • Remove SSLMode from the SP constructor in favor of setting on first use
  • Make a ConnectionPool Controller interface (receives state, informs parameters)
  • Add Executor to ConnectionPool
  • Split RSM notification functionality into a new class
  • Add HostGroup Controller impl (to tie together replSets)
Generated at Thu Feb 08 04:51:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.