[
https://issues.apache.org/jira/browse/SENTRY-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542933#comment-16542933
]
Hadoop QA commented on SENTRY-2310:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12931482/SENTRY-2310.001.patch
against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to apply patch (exit code 1):
error:
a/sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HMSFollower.java:
does not exist in index
error:
sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HMSFollower.java:
does not exist in index
error:
sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HMSFollower.java:
does not exist in index
The patch does not appear to apply with p0, p1, or p2
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/3961/console
This message is automatically generated.
> 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
>
>
> 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)
