You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Alex McLintock (JIRA)" <ji...@apache.org> on 2018/10/16 07:55:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16651275#comment-16651275 ] 

Alex McLintock commented on SENTRY-2310:
----------------------------------------

I am hitting this in production (with a slightly out of date version of Cloudera Impala). Obviously the long term fix is to upgrade Impala to a version with this patch. However I can't do that right away.

 

1) What is the impact to users? Do they see failures ? (Our users don't *seem* to be affected but I can't be sure I am not missing failures)

2) Are there any work-arounds or 'good behaviour' which I (and others with this problem) should follow.

 

Thanks.

> 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
>             Fix For: 2.1.0
>
>         Attachments: SENTRY-2310.001.patch, SENTRY-2310.002.patch, SENTRY-2310.003.patch, SENTRY-2310.004.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)