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

Posted to issues@sentry.apache.org by "kalyan kumar kalvagadda (JIRA)" <ji...@apache.org> on 2018/04/02 13:26:00 UTC

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

kalyan kumar kalvagadda created SENTRY-2195:
-----------------------------------------------

             Summary: 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
             Fix For: 2.1.0


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 notifcation ID row lock and delay notification processing. It should avoid this by just reading existing notifications.





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