[MCOL-1299] WriteEngineServ failure triggers stuck transactions Created: 2018-03-23 Updated: 2022-11-05 Resolved: 2022-11-05 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrew Hutchings (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
If WriteEngineServ fails mid-transaction then the transaction gets held open forever. This means the lock is held open until there is manual intervention. This affects both DMLProc and the bulk write API as they have no way of rolling back the transaction without WriteEngineServ running. WriteEngineServ should track this and initiate rollback when restarting. At the moment only DMLProc initiates rollback on restart. |
| Comments |
| Comment by Todd Stoffel (Inactive) [ 2022-11-05 ] |
|
Item is out of date. Closing due to inactivity. If you feel this was done in error please open a new ticket. |