Elasticsearch7.4.2 takes too long to form a cluster

[weekyuan]

hi，all：
When I deploy a brand new ealsticsearch cluster, it's always difficult to quickly form a whole.After some nodes form a cluster, other individual nodes wait for several hours and have not yet joined them.This has not happened in versions prior to 7.0
I tried to close all nodes and clean up the data directory before starting. I found that the nodes that could not join the cluster can join the cluster normally, but the normal nodes can not join the cluster.

There are usually several tips for not being able to join a cluster.

1. [m06] failed to join {m02}
   2.Caused by: org.elasticsearch.transport.ConnectTransportException: [m06][xxxx:9300] general node connection failure
   3.Caused by: org.elasticsearch.transport.TransportException: handshake failed because connection reset
   4.Caused by: java.io.IOException: Connection timed out: xxxx/xxxx:9300
   Caused by: java.io.IOException: Connection timed out
   5.Caused by: java.io.IOException: Connection reset by peer: xxxx/xxxx:9300
   Caused by: java.io.IOException: Connection reset by peer
   6.[m06] last failed join attempt was 1.9s ago, failed to join {m02}
   7.Caused by: org.elasticsearch.transport.ConnectTransportException: [m06][xxxx:9300] a channel closed while connecting

I make sure there are no special entries on the configuration, and the wrong 9300 port can also be telnet.

[weekyuan]

Request support, please help me, thank you!

[Christian_Dahlqvist]

Please share your configuration. Be aware that there are a number of settings that have chnaged between 6.X and 7.X, so make sure you read the documentation.

[weekyuan]

<

================== Elasticsearch Configuration ===================

---------------------------------- Cluster -----------------------------------

cluster.name: games

------------------------------------ Node ------------------------------------

node.name: m01

----------------------------------- Paths ------------------------------------

path.data: "/data1/elasticmaster/data"
path.logs: "/data1/elasticmaster/log"

----------------------------------- Memory -----------------------------------

bootstrap.memory_lock: true

---------------------------------- Network -----------------------------------

network.host: 10.142.114.120
http.port: 9200
transport.port: 9300-9400

--------------------------------- Discovery ----------------------------------

discovery.seed_hosts:
- 10.142.114.120:9300
- 10.142.114.121:9300
- 10.142.114.122:9300
- 10.142.114.243:9300
- 10.142.114.242:9300
- 10.142.100.51:9300
- 10.142.100.52:9300
- 10.142.107.71:9300
cluster.initial_master_nodes:
- m01
- m02
- m03
- m04
- m05
- m06
- m07
- m08

---------------------------------- Gateway -----------------------------------

gateway.recover_after_nodes: 5

---------------------------------- Various -----------------------------------

bootstrap.system_call_filter: false
action.destructive_requires_name: true

DEBUG

##logger.org.elasticsearch.discovery: TRACE
##logger.org.elasticsearch.transport: TRACE
##logger.org.elasticsearch.cluster.coordination: TRACE

---------------------------------- Security -----------------------------------

xpack.security.enabled: true
xpack.security.audit.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: elastic-certificates.p12
xpack.security.transport.ssl.cipher_suites: "TLS_RSA_WITH_AES_256_GCM_SHA384"
/>

Thanks for the reply, the above is my configuration information. I have indeed reviewed the configuration documentation repeatedly. But I really can't find the reason why I can't form a whole. Please also assist in troubleshooting, thank you very much!