[
https://issues.apache.org/jira/browse/DERBY-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557470#action_12557470
]
quartz commented on DERBY-1068:
-------------------------------
Thanks for the explanation.
The error message I pasted here says 'deadlock'.
That's is happening in our labs and at customers so that is not a fluke.
Our table is a "rolling" one, i.e. we have 1 record per 5 minutes, for 3 months.
That is 288*90 rows. Every hour we delete the excess of 90 days, i.e. generally
12 rows.
The compress of the 40 MB table takes less than 10 seconds.
Anyway, I just cannot understand how it got to 480 MB.... :-/
I will see if we can reproduce with simple code.
> change of store contract: online compress operations should not share any
> locks with user transactions
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1068
> URL: https://issues.apache.org/jira/browse/DERBY-1068
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Reporter: Andreas Korneliussen
> Assignee: Mike Matrigali
> Priority: Minor
>
> Propose to add the following to the store contract:
> * truncate and compress requires exclusive table locking
> * the truncate, purge and compress operations do not share any locks with
> user transactions
> Currently the store implementation allows users to share locks in truncate
> and possibly purge.
> This request is driven by:
> http://www.nabble.com/conflict-detection-strategies-t1120376.html#a2938142
> and:
> http://www.nabble.com/RowLocation-contract-from-storage-engine-t1142235.html#a2994156
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
