[
https://issues.apache.org/jira/browse/SENTRY-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156380#comment-16156380
]
Hadoop QA commented on SENTRY-1928:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12885722/SENTRY-1928.3.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/3259/console
This message is automatically generated.
> HMSFollower should close HMS connections when an error to HMS occurs
> --------------------------------------------------------------------
>
> Key: SENTRY-1928
> URL: https://issues.apache.org/jira/browse/SENTRY-1928
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Priority: Critical
> Attachments: SENTRY-1928.1.patch, SENTRY-1928.2.patch,
> SENTRY-1928.3.patch
>
>
> Sometimes the HMSFollower fails getting notifications from a HMS-HA
> environment because of SocketTimeoutExceptions. When this exception happens,
> the HMSFollower does not close such connection and it attempts to get
> notifications from the same HMS service causing a deadlock between HMS sync
> notifications listener and Sentry.
> We should close the current HMS connections and re-connect to another HMS
> service if this SocketTimeoutException happens or any other error with the
> HMS happens.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
