sentry-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kalyan kumar kalvagadda (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SENTRY-2310) Sentry is not be able to fetch full update subsequently, when there is HMS restart in the snapshot process.
Date Mon, 16 Jul 2018 17:56:00 GMT

     [ https://issues.apache.org/jira/browse/SENTRY-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

kalyan kumar kalvagadda updated SENTRY-2310:
--------------------------------------------
    Attachment: SENTRY-2310.004.patch

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

Mime
View raw message