[
https://issues.apache.org/jira/browse/SENTRY-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008437#comment-16008437
]
Alexander Kolbasov commented on SENTRY-1765:
--------------------------------------------
The root cause is incorrect handling of notification ID that should be fixed by
SENTRY-1669. But we should as well relax the requirement in CounterWait and
just ignore invalid updates there.
> CounterWait.update throw exception when input is old
> ----------------------------------------------------
>
> Key: SENTRY-1765
> URL: https://issues.apache.org/jira/browse/SENTRY-1765
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Na Li
> Assignee: Alexander Kolbasov
>
> 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)
