You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Arun Mahadevan (JIRA)" <ji...@apache.org> on 2016/04/07 09:42:25 UTC

[jira] [Commented] (STORM-1692) org.apache.storm.hbase.security.HBaseSecurityUtil#login uses broken double checked locking.

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

Arun Mahadevan commented on STORM-1692:
---------------------------------------

HBaseSecurityUtil uses legacyprovider.login(), which finally ends up in UserGroupInformation.loginUserFromKeytab() which modifies the static loginUser (currently logged in user) and this is causing issues if two tasks in the same jvm login with different credentials. 

The entire login method should rather be re-written to not affect the current user during login.

> org.apache.storm.hbase.security.HBaseSecurityUtil#login uses broken double checked locking. 
> --------------------------------------------------------------------------------------------
>
>                 Key: STORM-1692
>                 URL: https://issues.apache.org/jira/browse/STORM-1692
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-hbase
>            Reporter: Satish Duggana
>             Fix For: 2.0.0
>
>




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