You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/05/12 16:27:04 UTC
[jira] [Assigned] (SENTRY-1765) CounterWait.update throw exception
when input is old
[ https://issues.apache.org/jira/browse/SENTRY-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Na Li reassigned SENTRY-1765:
-----------------------------
Assignee: kalyan kumar kalvagadda (was: Na Li)
the latest change in SENTRY-1669 may fix this.
> 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: kalyan kumar kalvagadda
>
> 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)