Node previously joined cluster. After esrally, master not discovered yet

[wk3000sg (Kent Chew)]

I have 4 machines, each running 3 ES instances. (1 hot, 1 warm, 1 cold)
Each instance is tied to a few data.path
(Eg.
Hot pointing to "/ssd1,/ssd2",
warm pointing to "/hdd1, /hdd2",
cold pointing to "/hdd3, /hdd4").
The cluster was formed successfully

After running esrally several times to benchmark the performance, some of the instances started to disconnect from the cluster.
In the logs, i see "master not discovered" and cluster_uuid became "na".

I tried to restart the ES service but it still failed to join.
Do i have to clean up the data and try again? Why is this behaviour happening?

[warkolm (Mark Walkom)]

@wk3000sg

In the logs, i see "master not discovered" and cluster_uuid became " na ".

Please show the entire log.
Please make sure to format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you