[jira] [Commented] (AMBARI-14078) Metrics Collector startup is slow in Kerberized environment

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-14078:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12774437/AMBARI-14078.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4400//console

This message is automatically generated.

> Metrics Collector startup is slow in Kerberized environment
> -----------------------------------------------------------
>
>                 Key: AMBARI-14078
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14078
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.1.2
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-14078.patch
>
>
> PROBLEM
> Collector startup takes greater than 6mins even though the ApplicationHistoryServer is up in 2mins in secure cluster.
> Bug
> The collector startup script uses HBase shell to poll and check if the metrics schema is created. HBase shell takes a long time to respond in a secure environment without kinit.
> Fix
> Doing a "kinit" before starting up the metrics collector solves the performance issue



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