[
https://issues.apache.org/jira/browse/SENTRY-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543627#comment-16543627
]
Na Li commented on SENTRY-2310:
-------------------------------
[~kkalyan] We have SentryHMSClient to get full snapshot (have bug) and
HiveNotificationFetcher for delta change (not have bug). It is easy to create
bug and forget to update all places. What's the reason we have two classes
instead of one? If it is relative big change to marge two classes into one, we
can create a jira for that for now, and merge them later.
> 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
> Attachments: SENTRY-2310.001.patch, SENTRY-2310.002.patch,
> SENTRY-2310.003.patch
>
>
> 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)
