Error outputted in Flume log "_not part of the Cluster {interse}, ignoring…__"


The following error can be outputted in Flume log(s):

  • [elasticsearch[_client_][generic][T#1](org.elasticsearch.client.transport.TransportClientNodesService$SimpleNodeSampler.doSample:429) - node {#transport# - 2}{IE05zl0aSoCv2nfSfOrlTg}{SEARCH_NODE_FQDN}{XXX.XXX.XXX.XXX:9300} not part of the Cluster {interse}, ignoring…

The error can be outputted in the following log(s):

  • flume-interset_<ds>_events_<did>_<tid>_es.log


This is caused by an incorrect Elasticsearch cluster name that does not exist and most likely entered during the flume configuration creation.

Resolution Steps

NOTE: This information is only useful for CSV data ingest using Flume

There are two steps to take in order to resolve the issue:

  • Validate Elasticsearch cluster name
  • Validate Elasticsearch cluster name in Flume configuration/Regenerate Flume ingest configuration

Validate Elasticsearch cluster name

  1. SSH to the SEARCH NODE as the Interset User.
  2. Type in the following command to retrieve the Elasticsearch cluster name as it will be needed in the following step:
    • curl -ks -X GET http<s>://<SEARCH_NODE_FQDN>:9200 | grep cluster_name
  3. The output value will look similar to the following:
    • “cluster_name” : “interset”,
  4. Please make note of the cluster_name value as it will be needed in the next step.

Below are two options that may resolve the Elasticsearch cluster name issue:

  • Validate Elasticsearch cluster name in Flume configuration
  • Regenerate Flume configuration

NOTE: If “Validate Elasticsearch cluster name in Flume configuration” option becomes too difficult, it is recommended to regenerate the Flume config to minimize mistakes. 

Validate Elasticsearch cluster name in Flume configuration

  1. Open up a web browser and navigate to the Ambari UI URL:
  2. Log in to the Ambari UI as the Ambari admin. The default credentials for the Ambari admin user are as follow:
    • Username: admin
    • Password: admin
  3. Once logged in, click on Flume (from component list)
  4. In Flume, click on the Configs tab
  5. Click the Groups dropdown and select Ingest
  6. Under the flume.conf section, copy the Flume configuration to a text editor.
  7. In the text editor, look for the following 2 parameters:
    • sinks.esSink.clusterName
    • sinks.esSink.serializer.clusterName
    • sinks.esSink.clusterName
    • sinks.esSink.serializer.clusterName
  8. Modify/validate the value specified for each parameter set to the Elasticsearch cluster name
    • EXAMPLE:
      • sinks.esSink.clusterName = interset
  9. After the Elasticsearch cluster name value is modified/validated, copy the flume configuration from the text editor and replace the flume configuration in the flume.conf section in the Ambari UI.
  10. Once the configuration has been replaced, click Save to continue, and then OK.
  11. Click the Restart button at top of the webpage and select Restart All Affected.
  12. Click Confirm Restart All to restart Flume and use the new configuration
  13. Click OK once Flume restarts successfully

Regenerate Flume ingest configuration

  1. To regenerate the Flume ingest configuration, please see the Configure a New Data Source section in the Interset <version> Installation and Configuration guide.

Applies To

  • Interset 5.4.x or higher 
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request