You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/14 20:33:00 UTC

[jira] [Commented] (ASTERIXDB-2131) An Aborted Metadata Txn Leads to Invalid Active Ops

    [ https://issues.apache.org/jira/browse/ASTERIXDB-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204810#comment-16204810 ] 

ASF subversion and git services commented on ASTERIXDB-2131:
------------------------------------------------------------

Commit e2cf9c2715b74d79cb2185ec862bd12d2bfbb7a5 in asterixdb's branch refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=e2cf9c2 ]

[ASTERIXDB-2131][TX] Do Not Reset Active Ops For Aborted Metadata Txn

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- Do not reset the primary index operation tracker active operations
  count if the metadata transaction was aborted.
- Add test cases.

Change-Id: Iee47aca1be0675b704ed9f176d9e10daef1cfc7f
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2071
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Ian Maxon <im...@apache.org>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <ba...@gmail.com>


> An Aborted Metadata Txn Leads to Invalid Active Ops
> ---------------------------------------------------
>
>                 Key: ASTERIXDB-2131
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2131
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: TX - Transactions
>            Reporter: Murtadha Hubail
>            Assignee: Murtadha Hubail
>            Priority: Critical
>
> 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:
> {code:java}
> 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]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)