Collector failed to collect data – How to solve related issues

Collector failed to collect data – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Collector failed to collect data ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Collector [{}] failed to collect data” classname is Collector.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 return doCollect(convertNode(timestamp; clusterService.localNode()); interval; clusterState);
            }
        } catch (ElasticsearchTimeoutException e) {
            logger.error((Supplier>) () -> new ParameterizedMessage("collector [{}] timed out when collecting data"; name()));
        } catch (Exception e) {
            logger.error((Supplier>) () -> new ParameterizedMessage("collector [{}] failed to collect data"; name()); e);
        }
        return null;
    }

    protected abstract Collection doCollect(MonitoringDoc.Node node;




 

Run the Check-Up to get a customized report like this:

Analyze your cluster