[SERVER-36515] Make ClusterCommitTransaction only send commit to participant shards Created: 07/Aug/18 Updated: 27/Sep/18 Resolved: 15/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, ClusterCommitTransaction sends commitTransaction to all shards, since this was sufficient for the single shard case. To unblock basic testing of global snapshot reads across multiple shards (but not all shards), it should be changed to only target the shards in the participant list.
|