[DERBY-4054] Multithreaded clob update with exclusive table locking causes table growth that is not reclaimed

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.1.1
• Component/s: Store
• Labels: derby_triage10_11
• Urgency: Normal
• Issue & fix info: High Value Fix
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 12/Feb/09 17:50
• Updated: 03/Jul/13 15:26

Description

If I do a multithreaded clob update which gets an exclusive table lock on the table, space will not be reclaimed. This case is similar to DERBY-4050 except that the test gets an exclusive table lock and the growth happens whether or not the update is synchronized. I will add a disabled test for this to ClobReclamationTest and reference this bug.

Issue Links

• is related to: DERBY-4050 Multithreaded clob update causes growth in table that does not get reclaimed
• is related to: DERBY-5356 Tracking for Derby space reclamation issues

Sub-Tasks

• If space reclamation cannot obtain container lock it will not retry getting the lock: Closed