[
https://issues.apache.org/jira/browse/SENTRY-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008600#comment-16008600
]
Hadoop QA commented on SENTRY-1765:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12867814/SENTRY-1765.001-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2691/console
This message is automatically generated.
> CounterWait.update should be less strict
> ----------------------------------------
>
> Key: SENTRY-1765
> URL: https://issues.apache.org/jira/browse/SENTRY-1765
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Na Li
> Assignee: Alexander Kolbasov
> Attachments: SENTRY-1765.001-sentry-ha-redesign.patch
>
>
> CounterWait.update is called 3 times when HMSFollower. When it is called
> after each notification event processing, the input ID is older than what's
> in CounterWait, and exception is thrown.
> Should we remove the place that causes the issue? Or/And we allow older value
> as input, and not throw exception?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
