[SERVER-85344] Check for matching read concern in txn metadata when added participant continues txn Created: 17/Jan/24 Updated: 02/Feb/24 Resolved: 02/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 8.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Israel Hsu | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Cluster Scalability 2024-2-5 |
| Participants: |
| Description |
|
When a shard receives a request with startOrContinueTransaction, resulting in the shard continuing the current transaction (it's already a participant), the shard checks that the request's txn metadata for read concern matches the txn's read concern. |
| Comments |
| Comment by Githook User [ 02/Feb/24 ] |
|
Author: {'name': 'Janna Golden', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: GitOrigin-RevId: bd87daf14fbc502a973012c80b0a84e303baad7c |