[
https://issues.apache.org/jira/browse/TEPHRA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Neumann updated TEPHRA-194:
-----------------------------------
Description:
Currently, if an invalid timeout (negative, or too long) is given, the Tx
manager throws an IllegalArgumentException. The thrift client will catch that
and apply the retry strategy. However, in this case, retry is pointless, and if
the strategy is, for example, exponential backoff, if introduces unneccessary
load and latency.
The service should instead throw a meaningful exception for that, so that the
client knows not to retry.
was:
Currently, if an invalid timeout (negative, or too long) is given, the Tx
manager throws an IllegalArgumentException. The thrift client will catch that
and apply the retry strategy. However, in this case, retry is pointless, and if
the strategy is, for example, exponential backoff, if introduces unneccessary
load and latency.
The service should instead throw a meaningful exception that.
> Transaction client should not retry startShort() if an invalid timeout is
> given
> --------------------------------------------------------------------------------
>
> Key: TEPHRA-194
> URL: https://issues.apache.org/jira/browse/TEPHRA-194
> Project: Tephra
> Issue Type: Bug
> Components: client
> Affects Versions: 0.9.0-incubating, 0.10.0-incubating
> Reporter: Andreas Neumann
> Assignee: Andreas Neumann
> Fix For: 0.10.0-incubating
>
>
> Currently, if an invalid timeout (negative, or too long) is given, the Tx
> manager throws an IllegalArgumentException. The thrift client will catch that
> and apply the retry strategy. However, in this case, retry is pointless, and
> if the strategy is, for example, exponential backoff, if introduces
> unneccessary load and latency.
> The service should instead throw a meaningful exception for that, so that the
> client knows not to retry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
