You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2017/05/12 17:45:04 UTC

[jira] [Updated] (SENTRY-1765) CounterWait.update should be less strict

     [ https://issues.apache.org/jira/browse/SENTRY-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Kolbasov updated SENTRY-1765:
---------------------------------------
    Summary: CounterWait.update should be less strict  (was: CounterWait.update throw exception when input is old)

> 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
>
> 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)