[
https://issues.apache.org/jira/browse/SENTRY-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162206#comment-16162206
]
Hadoop QA commented on SENTRY-1940:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12886503/SENTRY-1940.01.patch
against master.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/3280/console
This message is automatically generated.
> Sentry should time out threads waiting for notifications
> --------------------------------------------------------
>
> Key: SENTRY-1940
> URL: https://issues.apache.org/jira/browse/SENTRY-1940
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Alexander Kolbasov
> Assignee: Alexander Kolbasov
> Labels: bite-sized, newbie
> Attachments: SENTRY-1940.01.patch
>
>
> HMS synchronizes with Sentry by sending special sync requests waiting for
> notifications to be processed. When notification processing is delayed, a lot
> of Sentry service threads can be tied up waiting. HMS eventually times out
> these requests but Sentry doesn't, so if notifications are delayed, all
> service threads may become busy for a long time.
> We must introduce a timeout on the Sentry side as well to avoid this scenario.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
