You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2016/01/13 10:34:39 UTC

[jira] [Updated] (AMBARI-14646) Streamline the usage pattern for kinit'ing in code

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

Andrew Onischuk updated AMBARI-14646:
-------------------------------------
    Attachment: AMBARI-14646.patch

> Streamline the usage pattern for kinit'ing in code
> --------------------------------------------------
>
>                 Key: AMBARI-14646
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14646
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-14646.patch
>
>
> Library methods such as `ExecuteHadoop` has the ability to call kinit if
> appropriate parameters are specified but it looks like its not being used.
> This results in bugs as folks
> may forget to add the statement to kinit at the right place.
> We should look into all location where `ExecuteHadoop` is used and check if
> the usage can be cleaned up. There are about 6 services that use
> `ExecuteHadoop` so it should not be a large task and we should use the
> inherent ability to kinit that is available.
> If for some reason it can't be used then lets remove the code to kinit from
> the implementation of `ExecuteHadoop`.



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