[DOCS-16307] Investigate changes in SERVER-79091: Write endOfTransaction oplog entry to transaction coordinator shard Created: 08/Aug/23 Updated: 22/Jan/24 |
|
| Status: | Backlog |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | backlog, feature, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 23 weeks ago | ||||||||
| Description |
|
Original Downstream Change Summary Now new endOfTransaction change stream event is supported for multi shard transaction. It is still hidden under a feature flag. Description of Linked TicketCurrently, as change streams target all the shards, we can write end of transaction oplog entry just to the transaction coordinator shard. In the future, we will also implement SERVER-78271 and SERVER-78273 to support change stream targeting. |
| Comments |
| Comment by Katya Kamenieva [ 30/Aug/23 ] |
|
not 7.1. will be released as part of [PM-2782] in some later version |