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

["Arjun Mishra (JIRA)" <ji...@apache.org>]

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

Arjun Mishra edited comment on SENTRY-2310 at 10/16/18 2:54 PM:
----------------------------------------------------------------

Hi [~alexmc_bp]. You would have to upgrade Sentry to have this fix. 

# What is the impact to users?
## Impact is on HDFS sync and HMS threads being blocked. You're Impala jobs are probably running slow at this point. Sentry is not able to fetch or process any notifications from HMS
# Are there any work-arounds or 'good behaviour'
## Work around is to restart sentry 


was (Author: arjunmishra13):
Hi [~alexmc_bp]. You would have to upgrade Sentry to have this fix. 

# What is the impact to users?
## Impact is on HDFS sync and HMS threads being blocked. You're Impala jobs are probably running slow at this point. Sentry is not able to fetch or process any notifications from HMS
# Are there any work-arounds or 'good behaviour' which
## Work around is to restart sentry 

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