[
https://issues.apache.org/jira/browse/AMBARI-14078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-14078:
---------------------------------------
Description:
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
was:
PROBLEM
Collector startup takes greater than 6mins even though the
ApplicationHistoryServer is up in 2mins in secure cluster.
Bug
HBase shell takes a long time to respond in a secure environment.
Fix
Doing a "kinit" before starting up the hbase shell seems to make it a lot
faster.
> 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
>
>
> 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)
