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

Posted to issues@sentry.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2017/09/06 22:05:00 UTC

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

     [ https://issues.apache.org/jira/browse/SENTRY-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergio Peña reassigned SENTRY-1928:
-----------------------------------

    Assignee: Sergio Peña

> 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
>
> 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)