Support Questions

Find answers, ask questions, and share your expertise
Announcements
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.

some of the ambari metrics display 'no data available'.

some of the ambari metrics display 'no data available'.

Getting below error message in ambari-metrics-collector.log

Caused by: java.io.IOException: maxStamp is smaller than minStamp at org.apache.hadoop.hbase.io.TimeRange.<init>(TimeRange.java:80) at org.apache.phoenix.util.ScanUtil.intersectTimeRange(ScanUtil.java:861) at org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:267) ... 57 more 2018-03-07 04:16:56,736 WARN org.apache.hadoop.yarn.webapp.GenericExceptionHandler: INTERNAL_SERVER_ERROR java.lang.RuntimeException: java.io.IOException: maxStamp is smaller than minStamp at org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:273) at org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:216) at org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:281) at org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:266) at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) at org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:265) at org.apache.phoenix.jdbc.PhoenixPreparedStatement.executeQuery(PhoenixPreparedStatement.java:186) at org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.PhoenixHBaseAccessor.getAggregateMetricRecords(PhoenixHBaseAccessor.java:1030) at org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.getTimelineMetrics(HBaseTimelineMetricStore.java:256) at org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:359) at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606)

Restarted Metrics Monitors and Metrics Collector, but still same issue.

I need some help please.

Thanks

1 REPLY 1

Super Mentor

@Srini K

Which version of ambari are you using?

# rpm -qa | grep ambari

I have seen similar errors in very old version of Ambari Metrics Collector: https://issues.apache.org/jira/browse/AMBARI-13049

By any chance you have upgraded your Ambari / Metrics Collector recently?

Is there a Client API which is attempting to make a call to AMS Rest APIs with incorrect start & end stamps?

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.