[HIVE-26409] Assign NO_TXN operation type for table in global locks for scheduled queries

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-2
• Labels: pull-request-available
• Assignee: Sourabh Badhya
• Reporter: Sourabh Badhya
• Created: 19/Jul/22 07:51
• Updated: 16/Nov/22 13:50
• Resolved: 21/Jul/22 13:24

Description

NO_TXN operation type has to be assigned while acquiring locks for the table in global locks because this will not add records to COMPLETED_TXN_COMPONENTS table. Currently the record introduced by this lock had writeId as NULL. There was a situation which lead to large number of records in COMPLETED_TXN_COMPONENTS table because these records had writeId as NULL which weren't deleted up by AcidHouseKeeperService/Cleaner and this subsequently lead to OOM errors.

Issue Links

• links to: GitHub Pull Request #3454