Es newspaper the same ID but is a different node instance

ES startup report as follows error
[2018-10-06xxx3:12:15,871] [INFO] [O.e.d.z.zendiscovery] [ES3] failed to send join request to master [{Es2}{b_jks2_ft9kmjkelxz8omg}{8iamxxftq_ isqhb3gmvc4g}{172.16.0.6}{172.16.0.6:9300}{ml.machine_memory=67556114432, Ml.max_open_jobs=20, xpack.installed= True, ml.enabled=true}], reason [Remotetransportexception[[es2][172.16.0.6:9300][internal:discovery/zen/join]]; Nested:illegalargumentexception[can ' t add node {es3}{b_jks2_ft9kmjkelxz8omg}{h-xxxkptat2mgujszilxrja}{172.16.0.22 }{172.16.0.22:9300}{ml.machine_memory=67556106240, Ml.max_open_jobs=20, Xpack.installed=true, ml.enabled=true}, Found existing node {Es2}{b_jks2_ft9kmjkelxz8omg}{8iamxxftq_isqhb3gmvc4g}{172.16.0.6}{172.16.0.6:9300}{ml.machine _memory=67556114432, Xpack.installed=true, ml.max_open_jobs=20, ml.enabled=true} with the same ID but is a different node Instance]; ]

with the same id but is a different node instance具有相同的id但是是不同的节点实例

Reason:
When I deployed the ES cluster 1th node, I for the convenience, directly from the ES cluster 1th node rsync es directory to the ES cluster 2nd node, so when the 2nd node start the service will be reported as the error, and before the 1th node when the test has produced data, So if you copy this data, you'll get an error, not even master.

Here's how to fix it
Delete the nodes directory of the 2nd node
rm -rf /data/elasticsearch/data/nodes/

Attention
If it is already joined to the cluster ES, in the modification of the file is also reported this error, you need to delete the node data file and then restart

Es newspaper the same ID but is a different node instance