[jira] [Resolved] (TEPHRA-188) There should be a way to limit the transaction timeout

2016-10-07 Thread Andreas Neumann (JIRA)

 [ 
https://issues.apache.org/jira/browse/TEPHRA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Neumann resolved TEPHRA-188.

Resolution: Fixed

> 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)


[jira] [Commented] (TEPHRA-188) There should be a way to limit the transaction timeout

2016-10-07 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TEPHRA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1799#comment-1799
 ] 

ASF GitHub Bot commented on TEPHRA-188:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-tephra/pull/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)


[GitHub] incubator-tephra pull request #17: (TEPHRA-188) Allow to configure a limit f...

2016-10-07 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-tephra/pull/17


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---