You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Sailesh Mukil (JIRA)" <ji...@apache.org> on 2017/10/30 16:45:00 UTC

[jira] [Resolved] (IMPALA-5129) Use Kudu's Kinit code to avoid expensive fork

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

Sailesh Mukil resolved IMPALA-5129.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.11.0

Commit in:
https://github.com/apache/incubator-impala/commit/4592ed445e5cd946efbec8e40c73ed3e8162f3b2

> Use Kudu's Kinit code to avoid expensive fork
> ---------------------------------------------
>
>                 Key: IMPALA-5129
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5129
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Security
>            Reporter: Sailesh Mukil
>            Assignee: Sailesh Mukil
>              Labels: security
>             Fix For: Impala 2.11.0
>
>
> Impala does a kinit by doing a RunShell() command which basically forks the entire process (potentially expensive) and execs the 'kinit' command.
> KuduRPC avoids the fork by calling into libkrb programatically. Since we eventually will be pulling in KuduRPC to Impala, we can get rid of the fork and call into the appropriate KuduRPC code.



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