[
https://issues.apache.org/jira/browse/AMBARI-14078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028892#comment-15028892
]
Hudson commented on AMBARI-14078:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3917 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3917/])
AMBARI-14078 Metrics Collector startup is slow in Kerberized environment (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b9f87c180c4f8bf09a92111b9e9f1b475451c88c])
*
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py
*
ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-collector
> 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)
