Do not abort all yielding memtx transactions when DDL is committed #10377
Description
Currently, any DDL operation aborts all yielding memtx transactions, even those that are not directly affected by it:
local fiber = require('fiber')
box.cfg{
log_level = 'warn',
memtx_use_mvcc_engine = true,
}
local s = box.schema.space.create('test')
s:create_index('pk')
box.begin()
s:insert({1})
local f = fiber.new(box.schema.space.create, 'test2')
f:set_joinable(true)
f:join()
box.commit()
os.exit(0)Output:
2024-08-07 12:49:27.531 [143562] main/114/lua memtx_tx.c:700 W> Transaction committing DDL (id=392) has aborted another TX (id=391)
2024-08-07 12:49:27.532 [143562] main test.lua:18 E> ER_TRANSACTION_CONFLICT: Transaction has been aborted by conflict
2024-08-07 12:49:27.532 [143562] main F> fatal error, exiting the event loop
This is caused by the following code:
tarantool/src/box/memtx_engine.cc
Lines 623 to 624 in 625afe4
In contrast to memtx, Vinyl aborts only affected transactions when a DDL operation is committed, see commit d3e1236. We should do something similar in memtx.