You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "kalyan kumar kalvagadda (JIRA)" <ji...@apache.org> on 2018/07/13 11:39:00 UTC
[jira] [Updated] (SENTRY-2310) Sentry is not be able to fetch full
update subsequently, when there is HMS restart in the snapshot process.
[ https://issues.apache.org/jira/browse/SENTRY-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
kalyan kumar kalvagadda updated SENTRY-2310:
--------------------------------------------
Summary: Sentry is not be able to fetch full update subsequently, when there is HMS restart in the snapshot process. (was: Sentry is not be able to fetch full updates when there is HMS restart in the snapshot process.)
> Sentry is not be able to fetch full update subsequently, when there is HMS restart in the snapshot process.
> ------------------------------------------------------------------------------------------------------------
>
> Key: SENTRY-2310
> URL: https://issues.apache.org/jira/browse/SENTRY-2310
> Project: Sentry
> Issue Type: Bug
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Priority: Major
>
> If the communication between sentry and HMS goes down for any reason while sentry is fetching full update from HMS, SentryHMSClient in HMSFollower would be left with a reference to closed socket. As sentry is not handling the failure and closing the SentryHMSClient, it continues using the same SentryHMSClient. This will result in "java.net.SocketException: Broken pipe" as the client tries to write on socket that is closed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)