[
https://issues.apache.org/jira/browse/SENTRY-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543491#comment-16543491
]
kalyan kumar kalvagadda edited comment on SENTRY-2310 at 7/13/18 5:34 PM:
--------------------------------------------------------------------------
[~arjunmishra13] I have proposed two options. This option-1 in my proposals.
Only concern that I have with this is that we have to me careful and make sure
that new functionality added in HMSFollower should also handle the exceptions
and update the client accordingly.
I will be posting the changes for review.
was (Author: kkalyan):
[~arjunmishra13] I have proposed two options. This option-1 in my proposals.
Only concern that I have with this is that we have to me careful and make sure
that new functionality added in HMSFollower should also handle the exceptions
and update the client accordingly.
> 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)
