[jira] [Comment Edited] (SENTRY-2310) Sentry is not be able to fetch full updates when there is HMS restart in the snapshot process.

["kalyan kumar kalvagadda (JIRA)" <ji...@apache.org>]

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

kalyan kumar kalvagadda edited comment on SENTRY-2310 at 7/13/18 11:37 AM:
---------------------------------------------------------------------------

I feel creating new connection every time(Option-2) is also a good option. It doesn't create much overhead.


was (Author: kkalyan):
I feel creating new connection every time is also a good option. It doesn't create much overhead.

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