[ASTERIXDB-2131] An Aborted Metadata Txn Leads to Invalid Active Ops

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Component/s: TX - Transactions
• Assignee: Murtadha Makki Al Hubail
• Reporter: Murtadha Makki Al Hubail
• Created: 13/Oct/17 15:31
• Updated: 16/Oct/17 00:48
• Resolved: 16/Oct/17 00:48

Description

When a metadata transaction is aborted, the number of active operations on the primary index are decremented twice, one time when the job abort log is written and the other when the transaction completes its abortion. This will result in the following exception when the index is accessed the next time:

Caused by: org.apache.hyracks.api.exceptions.HyracksDataException: The number of active operations cannot be negative!
	at org.apache.asterix.common.context.PrimaryIndexOperationTracker.completeOperation(PrimaryIndexOperationTracker.java:85) ~[asterix-common-0.9.3-SNAPSHOT.jar:0.9.3-SNAPSHOT]
	at org.apache.asterix.metadata.MetadataNode.deleteTupleFromIndex(MetadataNode.java:835) ~[asterix-metadata-0.9.3-SNAPSHOT.jar:0.9.3-SNAPSHOT]
	at org.apache.asterix.metadata.MetadataNode.dropNodegroup(MetadataNode.java:734) ~[asterix-metadata-0.9.3-SNAPSHOT.jar:0.9.3-SNAPSHOT]