Hi Team,
I am facing strange behavior in prod environment.
I used same configuration in prod and DR servers but in prod its working fine, in DR elasticserch is not connecting to different node when I am configuring cluster.
in logs i saw its connecting to different port. i have mentioned 9200 in .yml file but its taking 9300 port.
But in prod servers its different behaviour. its taking 9200 port .
.yml file -
#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 -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
network.host: 0.0.0.0
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
**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: ["XXXX.YYYY.ab","XXXXX2.YYYYY.ab"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
cluster.initial_master_nodes: ["XXXX.YYYY.ab"]
#
# For more information, consult the discovery and cluster formation module documentation.
from log file -
[2022-11-15T10:46:30,481][INFO ][o.e.t.n.NettyAllocator ] [machine-46] creating NettyAllocator with the following configs: [name=elasticsearch_configured, chunk_size=1mb, suggested_max_allocation_size=1mb, factors={es.unsafe.use_netty_default_chunk_and_page_size=false, g1gc_enabled=true, g1gc_region_size=8mb}]
[2022-11-15T10:46:30,510][INFO ][o.e.i.r.RecoverySettings ] [machine-46] using rate limit [40mb] with [default=40mb, read=0b, write=0b, max=0b]
[2022-11-15T10:46:30,549][INFO ][o.e.d.DiscoveryModule ] [machine-46] using discovery type [multi-node] and seed hosts providers [settings]
[2022-11-15T10:46:31,858][INFO ][o.e.n.Node ] [machine-46] initialized
[2022-11-15T10:46:31,859][INFO ][o.e.n.Node ] [machine-46] starting ...
[2022-11-15T10:46:31,887][INFO ][o.e.x.s.c.f.PersistentCache] [machine-46] persistent cache index loaded
[2022-11-15T10:46:31,888][INFO ][o.e.x.d.l.DeprecationIndexingComponent] [machine-46] deprecation component started
**[2022-11-15T10:46:32,005][INFO ][o.e.t.TransportService ] [machine-46] publish_address {10.00.00.00:9300}, bound_addresses {[::]:9300}**
[2022-11-15T10:46:32,247][INFO ][o.e.b.BootstrapChecks ] [machine-46] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2022-11-15T10:46:32,251][INFO ][o.e.c.c.ClusterBootstrapService] [machine-46] this node has not joined a bootstrapped cluster yet; [cluster.initial_master_nodes] is set to XXXX.yyyy.ab
[2022-11-15T10:46:32,260][INFO ][o.e.c.c.ClusterBootstrapService] [machine-46] skipping cluster bootstrapping as local node does not match bootstrap requirements: [XXXX.yyyy.ab]
[2022-11-15T10:46:42,267][WARN ][o.e.c.c.ClusterFormationFailureHelper] [machine-46] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [DSPCLTIBELST1.network.sa] to bootstrap a cluster: have discovered [{machine-46}{xGG_f_I6QxSV7BE4RyCKBA}{3SbUxDaUT8KNyZHFMkFzEQ}{machine-46}{10.97.12.46}{10.97.12.46:9300}{cdfhilmrstw}, {machine-45}{dXWgJGseQYSLT6poxxSaAw}{hICJAM41Sm6PH5rYVODK8Q}{machine-45}{10.00.10.00}{00.00.00.00:9300}{cdfhilmrstw}]; discovery will continue using [10.00.00.00:9300] from hosts providers and [{machine-46}{xGG_f_I6QxSV7BE4RyCKBA}{3SbUxDaUT8KNyZHFMkFzEQ}{machine-46}{10.97.12.46}{10.97.12.46:9300}{cdfhilmrstw}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
In yml i configured 9200 but its trying to use 9300.
Same configure file is working fine in another machine.