[SERVER-60773] DDL participant commands should ensure they are ran within a session after 6.0 branches out Created: 18/Oct/21 Updated: 29/Oct/23 Resolved: 17/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27 |
| Participants: |
| Description |
|
On 5.0.2, it was made that the following commands are ran with a sessionId & txnNumber attached: However, 5.0.0 binaries did not attach it yet. So for backwards compatibility, those commands do not enforce that they are run as a "retryable write". After 6.0 branches out, we will be guaranteed that no more binaries that do not attach the sessionId are in the cluster. This ticket is to enforce that those commands are run with sessionId & txnNumber |
| Comments |
| Comment by Githook User [ 17/Jun/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |