[jira] [Commented] (SENTRY-1928) HMSFollower should close HMS connections when an error to HMS occurs

["Sergio Peña (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SENTRY-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156091#comment-16156091 ] 

Sergio Peña commented on SENTRY-1928:
-------------------------------------

[~akolb] [~vamsee] Here's a bug causing a deadlock with HMS and Sentry. 

Question, should we close the HMS connections and re-connect to any kind of HMS connection error or just with SocketException and SocketTimeoutException?

> 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
>            Priority: Critical
>
> 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)