[
https://issues.apache.org/jira/browse/SENTRY-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542269#comment-16542269
]
kalyan kumar kalvagadda commented on SENTRY-2310:
-------------------------------------------------
There are two options here
# close the SentryHMSClient when there is an exception. Drawback with this
approach is that we need to make sure that this is done when ever new API's are
added to SentryHMSClient.
# Make sure that SentryHMSClient in HMSFollower is closed every time execution
of HMSFollower is done. Over head is that sentry would creating new connection
and closing it for every 500 milli sec.
> Sentry is not be able to fetch full updates 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)
