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 2018/09/13 16:44:00 UTC

[jira] [Updated] (SENTRY-2195) Sentry should avoid getting current notification ID from hive

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

Na Li updated SENTRY-2195:
--------------------------
    Fix Version/s:     (was: 2.1.0)

> Sentry should avoid getting current notification ID from hive
> -------------------------------------------------------------
>
>                 Key: SENTRY-2195
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2195
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 2.1.0
>            Reporter: kalyan kumar kalvagadda
>            Assignee: kalyan kumar kalvagadda
>            Priority: Major
>
> Sentry currently gets the current notification ID from HMS every run to check if sentry is out of sync. This introduces additional RPC revery time. Instead there are other checks that could be done to detect out-of-sync situations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)