[jira] [Updated] (RANGER-265) If Hive repository's connection is setup incorrectly then it can make policy manager unresponsive.

["Selvamohan Neethiraj (JIRA)" <ji...@apache.org>]

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

Selvamohan Neethiraj updated RANGER-265:
----------------------------------------
    Fix Version/s: 0.5.0

> If Hive repository's connection is setup incorrectly then it can make policy manager unresponsive.
> --------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-265
>                 URL: https://issues.apache.org/jira/browse/RANGER-265
>             Project: Ranger
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Alok Lal
>            Assignee: Alok Lal
>             Fix For: 0.5.0
>
>         Attachments: 0001-RANGER-265-Changed-TimedEventUtil-so-that-it-would-i.patch
>
>
> [Reporting on behalf of Abhay Kulkarni]
> If the connection of a hive repository is setup incorrectly in such a manner that connect call gets blocked, i.e. does not error out then it quickly leads to a buildup of connect threads inside policy manager.  And eventually it stops responding to both the service plugins and to user requests.
> The cause of the problem seems to be the incomplete implementation of the deferred/timed execution class.  While the problem was reported on Hive it could affect any component.  This problem could be fixed at several levels:
> - Server could timeout the connection call and then interrupt that thread.
> - Server code that opens client connections to various services could in turn change how the critical sections are structured so that this problem does not happen and/or connection attempts don't block if someone else is trying to get a connection, etc.
> - For not a fix that could have widest impact should be considered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)