[ https://issues.apache.org/jira/browse/HIVE-23052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Vary updated HIVE-23052: ------------------------------ Fix Version/s: 4.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to master. Thanks for the patch [~Marton Bod] and [~dkuzmenko] for the review! > Optimize lock enqueueing in TxnHandler > -------------------------------------- > > Key: HIVE-23052 > URL: https://issues.apache.org/jira/browse/HIVE-23052 > Project: Hive > Issue Type: Improvement > Reporter: Marton Bod > Assignee: Marton Bod > Priority: Major > Fix For: 4.0.0 > > Attachments: HIVE-23052.1.patch, HIVE-23052.10.patch, > HIVE-23052.11.patch, HIVE-23052.12.patch, HIVE-23052.13.patch, > HIVE-23052.14.patch, HIVE-23052.2.patch, HIVE-23052.3.patch, > HIVE-23052.4.patch, HIVE-23052.5.patch, HIVE-23052.6.patch, > HIVE-23052.7.patch, HIVE-23052.8.patch, HIVE-23052.8.patch, > HIVE-23052.8.patch, HIVE-23052.9.patch > > > * Reduce scope of next_lock_id select-for-update by moving the txn_component > inserts before the S4U + inserting the hive_locks entries before the S4U > (first with a temp ID, which will be replaced later in a single update). This > helps decrease the overall time that the next_lock_id table is locked, > thereby increasing concurrency > * Insert txn_components in a batch instead of one-by-one (also in > TxnHandler::addDynamicPartition) > * Increment next_lock_id and update hive_locks table in a single batch > statement > -- This message was sent by Atlassian Jira (v8.3.4#803005)