[SERVER-70777] Optionally pin TaskExecutorCursor's commands to same TCP connection Created: 21/Oct/22 Updated: 21/Apr/23 Resolved: 21/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Rosendahl | Assignee: | Backlog - Service Architecture |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | mongot-cross-team, phase-1-HA-decoupled-scaling | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||
| Backport Requested: |
v6.3
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Implement optional cursor pinning as described in |
| Comments |
| Comment by Shameek Ray [ 24/Oct/22 ] |
|
tyler.brock@gmail.com, amirsaman.memaripour@mongodb.com, and I have been discussing about this with kevin.rosendahl@mongodb.com. It seems that pinning a cursor to the connection initially used is new behavior that is necessary for the correctness of Search working with Load Balancers. This is also relevant for Milestone 2 of Operational Resilience gRPC. As such, Service Architecture plans to prioritize this for next quarter. alice.neff@mongodb.com thanks for the tag here! Was planning to reach out after our product sync. |
| Comment by Connie Chen [ 24/Oct/22 ] |
|
alice.neff@mongodb.com - can you provide more color on the motivation for why it needs to be completed for Q4? Are there any dependencies on the Atlas side? |
| Comment by Alice Neff [ 24/Oct/22 ] |
|
shameek.ray@mongodb.com can you confirm this work is scheduled for Q4? |