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

[jira] [Assigned] (SENTRY-1831) The MetastorePlugin SyncTask is leaking connection threads when read timed out issues are thrown

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

Alexander Kolbasov reassigned SENTRY-1831:
------------------------------------------

    Assignee: Arjun Mishra

> The MetastorePlugin SyncTask is leaking connection threads when read timed out issues are thrown
> ------------------------------------------------------------------------------------------------
>
>                 Key: SENTRY-1831
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1831
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: 1.8.0
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>             Fix For: 1.8.0
>
>
> The MetastorePlugin.SyncTask class is a thread running in the background in the HMS side that is used to keep HMS/Sentry in sync with HDFS, or any other words, it pushes a full HMS snapshot to Sentry every time Sentry is out-of-sync. 
> However when a timed out exception is thrown when sending the snapshot to Sentry, a retry happens in the next thread run() iteration. 
> The problem is that these exceptions do not terminate the Thrift thread sending the data, and a new retry will generate a new Thrift thread be created. We should close those threads by resetting the connection when an error occurs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)