You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2019/01/25 01:48:00 UTC
[jira] [Commented] (SENTRY-1904) TransactionManager should limit
the max time spent by transaction retry
[ https://issues.apache.org/jira/browse/SENTRY-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751797#comment-16751797 ]
Hadoop QA commented on SENTRY-1904:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12956213/SENTRY-1904.009.patch against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} mvn test exited 1
Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/4327/console
This message is automatically generated.
> TransactionManager should limit the max time spent by transaction retry
> -----------------------------------------------------------------------
>
> Key: SENTRY-1904
> URL: https://issues.apache.org/jira/browse/SENTRY-1904
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Alexander Kolbasov
> Assignee: kalyan kumar kalvagadda
> Priority: Major
> Attachments: SENTRY-1904.001.patch, SENTRY-1904.002.patch, SENTRY-1904.003.patch, SENTRY-1904.004.patch, SENTRY-1904.005.patch, SENTRY-1904.006.patch, SENTRY-1904.007.patch, SENTRY-1904.008.patch, SENTRY-1904.009.patch
>
>
> The TransactionManager uses exponential backoff strategy for transaction retries. This may cause some transactions to be delayed by a very long time. We should also have a constraint on the max time for a transaction so that we do not retry for too long.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)