-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Use the shared applier code to split a prepared transaction across workers and resolve those splits on commit or abort. Keep prepared batches serialized for now. Release the internal split sessions in the advancer only after all resolution work finishes, before publishing the completed batch, and retain the non-split path.
Include unit tests for transactions spanning multiple workers, commit and abort, and consecutive transactions on the same session. Add a jstest for a split prepared transaction. Check that split sessions are not released early or twice and do not remain allocated after resolution.