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

ASF GitHub Bot commented on TRAFODION-2150:
-------------------------------------------

GitHub user prashanth-vasudev opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/917

    [TRAFODION-2150] and [TRAFODION-2151] TM long prepare and chore thread 
Issues

    Queries such as drop schema cascase involve multiple DDL operations that 
take some time to process. This cause transaction commits to timeout and cause 
transaction aborts. Fix is to detect long prepare scenarios and continue to 
commit the transaction.
    
    Cleanup Chore thread calls were deprecated and required chore service 
constructs. This should help memory cleanup issues in end point co processor. 
This should also help some of the regression test failure we see in 
executor/TEST130

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/prashanth-vasudev/incubator-trafodion 
longPrepare

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/917.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #917
    
----
commit 30c8a83d1512667f5ecfe2c7384372f646f18ae3
Author: Prashant Vasudev <prashanth.vasu...@esgyn.com>
Date:   2017-01-19T00:11:33Z

    [TRAFODION-2150] and [TRAFODION-2151] TM long prepare and chore thread 
issues.

----


> Long commit prepare causes auto transaction abort.
> --------------------------------------------------
>
>                 Key: TRAFODION-2150
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2150
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: dtm
>    Affects Versions: 2.0-incubating
>            Reporter: Prashanth Vasudev
>            Assignee: Prashanth Vasudev
>
> Drop schema cascade scenario, there is a possibility of several table drops 
> which might take time. This causes transaction to be active for long time. 
> Under this scenario, transaction is automatically aborted. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to