@Jean_Robert_Alves you have to set it to globally to READ_COMMITTED as isolation level for MySQL. Camunda doesn’t change any of the db configurations.
The Isolation level’s can be set globally or session based on our requirements.
A change to global transaction characteristics requires the
SUPER privilege. Any session is free to change its session characteristics (even in the middle of a transaction), or the characteristics for its next transaction (prior to the start of that transaction).
To set the global isolation level at server startup, use the
--transaction-isolation=level option on the command line or in an option file. Values of
level for this option use dashes rather than spaces, so the permissible values are
REPEATABLE-READ , or
Similarly, to set the global transaction access mode at server startup, use the
--transaction-read-only option. The default is
OFF (read/write mode) but the value can be set to
ON for a mode of read only.
SET [GLOBAL | SESSION] TRANSACTION
transaction_characteristic [, transaction_characteristic] ...
ISOLATION LEVEL level
| READ COMMITTED
| READ UNCOMMITTED
| READ ONLY
For camunda we need isolation level as ,
SET GLOBAL TRANSACTION ISOLATION LEVEL READ COMMITTED;
Then run the below query:
SELECT @@GLOBAL.transaction_isolation, @@GLOBAL.transaction_read_only;