Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
4.0.0
Description
Enabling ACIDv1 on a cluster produces a central locking bottleneck for all table types, which is not always the intention.
The Hive locking for non-acid tables are advisory (i.e a client can write/read without locking), which means that the implementation does not offer strong consistency despite the lock manager consuming resources centrally.
Disabling this lock acquisition would improve the performance of non-ACID tables co-existing with a globally configured DbTxnManager implementation.