Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.7.5
-
None
Description
It is expected that ambari server should select another available metrics collector for metrics retrieval on current collector fail. But actually we have the next numerous exceptions. Of course in this case metrics are unavailable via ambari API.
2020-12-10 08:41:44,402 ERROR [pool-3-thread-1] ambari-event-bus:232 - Exception thrown by subscriber method onMetricsCollectorHostDownEvent(org.apache.ambari.server.events.MetricsCollectorHostDownEvent) on subscriber org.apache.ambari.server.controller.metrics.MetricsCollectorHAManager@470dea54 when dispatching event: MetricsCollectorHostDownEvent{eventType=METRICS_COLLECTOR_HOST_DOWN} java.lang.NullPointerException at org.apache.ambari.server.controller.metrics.CollectorHostDownRefreshCounter.testRefreshCounter(CollectorHostDownRefreshCounter.java:33) at org.apache.ambari.server.controller.metrics.MetricsCollectorHAClusterState.onCollectorHostDown(MetricsCollectorHAClusterState.java:117) at org.apache.ambari.server.controller.metrics.MetricsCollectorHAManager.onMetricsCollectorHostDownEvent(MetricsCollectorHAManager.java:126) at sun.reflect.GeneratedMethodAccessor569.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:87) at com.google.common.eventbus.Subscriber$SynchronizedSubscriber.invokeSubscriberMethod(Subscriber.java:144) at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:72) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Attachments
Issue Links
- links to