[SERVER-34570] Remove isSharded() checks from FSM transactions testing once sharded transactions are supported Created: 19/Apr/18 Updated: 06/Dec/22 Resolved: 08/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | nyc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, FSM testing has to add logic to make sure transactions are only run on replica sets. Once support is added for transactions in a sharded environment, isSharded() checks like these should be removed. |
| Comments |
| Comment by Max Hirschhorn [ 18/May/18 ] |
|
I don't think it is the TIG team's responsibility to enable any transaction tests to run against sharded clusters so I'm moving this ticket over to the Sharding team because they are responsible for the feature. |