Je suis un débutant sur Elasticsearch, et fan de cette solution de moteur avancée BIG DATA.
Mais, j'ai un gros problème sur le passage à l'échelle.
En effet, j'ai installé elasticsearch 7.1.1 sur trois machines virtuelles: Windows 10, ubuntu 18.04 et centos 7. Les machines communiquent parfaitement via le ping. Mais les nodes elasticsearch sur les 3 machines ne communiquent pas. Voici la configuration du fichier elasticsearch.yml de la michine ubuntu 18.04, cette configuration est identique sur toutes les autres machines sauf le node.name qui diffère:
# ======================== Elasticsearch Configuration =========================
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
# ---------------------------------- Cluster -----------------------------------
# Use a descriptive name for your cluster:
cluster.name: NTEM
# ------------------------------------ Node ------------------------------------
# Use a descriptive name for the node:
node.name: "node-1"
# Add custom attributes to the node:
#node.attr.rack: r1
# ----------------------------------- Paths ------------------------------------
# Path to directory where to store the data (separate multiple locations by comma):
path.data: /var/lib/elasticsearch
# Path to log files:
path.logs: /var/log/elasticsearch
# ----------------------------------- Memory -----------------------------------
# Lock the memory on startup:
#bootstrap.memory_lock: true
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
# Elasticsearch performs poorly when the system is swapping the memory.
# ---------------------------------- Network -----------------------------------
# Set the bind address to a specific IP (IPv4 or IPv6):
#xpack.security.enabled: true
network.host: 192.168.125.33
transport.port: 9300
# Set a custom port for HTTP:
#http.port: 9200
# For more information, consult the network module documentation.
# --------------------------------- Discovery ----------------------------------
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
discovery.seed_hosts: ["192.168.125.32:9300", "192.168.125.33:9300", "192.168.125.51"]
# Bootstrap the cluster using an initial set of master-eligible nodes:
cluster.initial_master_nodes: ["node-1", "node-2", "node-3"]
# For more information, consult the discovery and cluster formation module documentation.
# ---------------------------------- Gateway -----------------------------------
# Block initial recovery after a full cluster restart until N nodes are started:
#gateway.recover_after_nodes: 3
# For more information, consult the gateway module documentation.
# ---------------------------------- Various -----------------------------------
# Require explicit names when deleting indices:
#action.destructive_requires_name: true
Merci de pour votre attention et j'espère trouver une solution a ce problème sur lequel je bloque depuis une semaine.
Cordialement a vous