[
https://issues.apache.org/jira/browse/SENTRY-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502611#comment-16502611
]
Alexander Kolbasov commented on SENTRY-2250:
--------------------------------------------
We don't really need a thread pool since there is a single stream of
notifications, so a single thread is good enough. We just need to replace the
existing periodic executor with a thread that can be waken up by either
# Timer expiration
# New request coming
> Optimize the logic of fetching the notification_log entries
> -----------------------------------------------------------
>
> Key: SENTRY-2250
> URL: https://issues.apache.org/jira/browse/SENTRY-2250
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Priority: Major
>
> Currently sentry fetches entries from notification_log in HMS periodically.
> This could result in delay 0.5 sec to 1 sec in fetching the events and
> processing them.
> As HMS threads are blocked till sentry processes the notification events,
> this delay in processing notifications would result in delay in query
> executions.
>
> Proposal is to proactively fetch the notification log entires from HMS.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
