[SERVER-78839] Investigate changes needed in sharding POS services to use the new return value for instance lookup Created: 10/Jul/23  Updated: 12/Dec/23

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

Type: Task Priority: Major - P3
Reporter: Wenbin Zhu Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-78009 shardSvrCommitReshardCollection comma... Closed
is related to SERVER-78108 POS interface should expose its shutd... Closed
Assigned Teams:
Cluster Scalability
Participants:

 Description   

SERVER-78108 added a new return value for instance lookup in order to differentiate if the instance is not present at all or the node is stepped down/shutdown when lookup() returns a null instance. This ticket should investigate if sharding POS services should use this new return value and do different actions accordingly, in addition to SERVER-78009.



 Comments   
Comment by Jason Chan [ 14/Jul/23 ]

hey r.scott@mongodb.com, we didn't think it was erroneously assigned because SERVER-78108 (a request from sharding) introduced a new API change in order to fix a bug related to resharding. This ticket is for the sharding team to investigate whether other sharding implementations that make use of POS might need the same fix. Since Service Arch only provides the underlying infrastructure (PrimaryOnlyService) and sharding builds on top of it, we think the Sharding team would be best fit since this will be changes in sharding code.

Generated at Thu Feb 08 06:39:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.