[SERVER-63547] Investigate how overrideShardIdentity could differ at Config and shard servers Created: 10/Feb/22 Updated: 27/Oct/23 Resolved: 27/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding NYC |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Participants: |
| Description |
|
overrideShardIdentity when starting in read-only queryable backup mode queryableBackupMode mode is opposite between Config and Shard servers. Properly handling this requires to track down the actual usage of shardIdentity document and narrow down its handling to the server “role”. |
| Comments |
| Comment by Jack Mulrow [ 27/Feb/23 ] |
|
This option is used to support queryable backups and we've split supporting those with a catalog shard into PM-3244. |