[
https://issues.apache.org/jira/browse/SENTRY-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-2195:
--------------------------------------------
Description: 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. (was: With the recent changes that we made in
DbNotificationListener, whenever Sentry tries to get last notification ID from
HMS it can get blocked on the notification ID row lock and delay notification
processing. It should avoid this by just reading existing notifications.
Sentry currently gets the )
> 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
> Fix For: 2.1.0
>
>
> 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)
