Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Could not open template: /usr/lib/impala//www//legacy-metrics.tmpl

Solved Go to solution

Could not open template: /usr/lib/impala//www//legacy-metrics.tmpl

New Contributor

On Impala 2.2 after CDH 5.4.0 upgrade from CDH 5.3.3 (CentOS 6.6) I am getting IMPALA_STATESTORE_HEALTH has become bad error for each Impala Deamon node.

Going to the http://<server ip>:25000/jsonmetrics in the browser, gives the error: Could not open template: /usr/lib/impala//www//legacy-metrics.tmpl
There is no legacy-metrics.tmpl file in /usr/lib/impala/www folder.

http://<server ip>:25000/jsonmetrics returns correct json result on CDH 5.3.3 and there is also no legacy-metrics.tmpl in the folder.

Looking into source code shows a redirect to the file, but the file is nowhere to be found?

Status MetricGroup::Init(Webserver* webserver) {
if (webserver != NULL) {
Webserver::UrlCallback default_callback =
bind<void>(mem_fn(&MetricGroup::CMCompatibleCallback), this, _1, _2);
webserver->RegisterUrlCallback("/jsonmetrics", "legacy-metrics.tmpl",
default_callback, false);

Please advise.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Could not open template: /usr/lib/impala//www//legacy-metrics.tmpl

Rising Star

Have you upgraded Cloudera Manager at the same time? The way in which CM retrieves metric data from Impala changed in CDH5.4, and should be using /jsonmetrics?json as the URL.

2 REPLIES 2

Re: Could not open template: /usr/lib/impala//www//legacy-metrics.tmpl

Rising Star

Have you upgraded Cloudera Manager at the same time? The way in which CM retrieves metric data from Impala changed in CDH5.4, and should be using /jsonmetrics?json as the URL.

Re: Could not open template: /usr/lib/impala//www//legacy-metrics.tmpl

New Contributor

That was it, thank you!

 

yum repo file was pointing to the old Cloudera Manager repo. After fixin the yum repo file and 'yum update'

with refreshing CM on all nodes, problem was solved.

 

I am using packages not parcels.

Don't have an account?
Coming from Hortonworks? Activate your account here