[MCOL-1147] multiple mcsapi sessions use the same txnID Created: 2018-01-08 Updated: 2023-10-26 Resolved: 2018-01-08 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrew Hutchings (Inactive) | Assignee: | Jens Röwekamp (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2018-01 |
| Description |
|
mcsapi requests a new txnID every time, unfortunately it uses a fixed sessionID and DBRM gives an existing txnID if there is one open. This means that a multi-threaded mcsapi application could use the same txnID for two transactions. Causing one commit/rollback to commit/rollback both. |
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2018-01-08 ] |
|
This patch randomizes the sessionID which therefore causes unique txnIDs to be generated. For QA: a test has been added to the "commit" test in the built-in regression suite which triggers on this. |
| Comment by Jens Röwekamp (Inactive) [ 2018-01-08 ] |
|
Compiled and run tests through make check on Ubuntu 16.04. Everything passed. Merged it to develop. |