[ https://issues.apache.org/jira/browse/TEPHRA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553389#comment-15553389 ]
ASF GitHub Bot commented on TEPHRA-188: --------------------------------------- GitHub user anew opened a pull request: https://github.com/apache/incubator-tephra/pull/17 (TEPHRA-188) Allow to configure a limit for the transaction timeout the title says it all. You can merge this pull request into a Git repository by running: $ git pull https://github.com/anew/incubator-tephra tephra-188-tx-timeout-limit Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-tephra/pull/17.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 #17 ---- ---- > There should be a way to limit the transaction timeout > ------------------------------------------------------ > > Key: TEPHRA-188 > URL: https://issues.apache.org/jira/browse/TEPHRA-188 > Project: Tephra > Issue Type: Improvement > Components: api, manager > Affects Versions: 0.9.0-incubating > Reporter: Andreas Neumann > Assignee: Andreas Neumann > Fix For: 0.10.0-incubating > > > When clients start a transaction, they can give a custom timeout for the > transaction. If a client uses a really long timeout, then crashes and never > commits or invalidates, then this will remain an active transaction forever. > In some use cases, it is therefore desirable to impose a system-wide limit on > that timeout. > I am proposing to add a new property data.tx.max.timeout to the > configuration. This can be optional, but if set, it limits the custom > transaction timeout for startShort(int timeout). -- This message was sent by Atlassian JIRA (v6.3.4#6332)