[SERVER-69546] In catalog shard POC catalog client should not take read concern arg Created: 08/Sep/22 Updated: 03/Oct/22 Resolved: 03/Oct/22 |
|
| 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: | Andrew Shuvalov (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding 2022-09-19, Sharding 2022-10-03, Sharding 2022-10-17 |
| Participants: | |
| Story Points: | 2 |
| Description |
|
The method ShardRemote::_exhaustiveFindOnConfig() requires the majority read concern. As catalog client is converted to fully remote thus always using ShardRemote, it must always use majority read concern. |