When the nodes leave and start at the same time in a large-capacity consul cluster, some member states will continue to keep leaving, not alive.

[yangjunmyfm192085]

I am in a consul scenario with 3 servers and 150 clients.
When 150 clients leave at the same time and restart, some member states show leaving
Further analysis, the following scenarios appear

• Node A and Node B are both rebooted
• After node A starts, it receives the leave message from B, and A caches the type and ltime of the message to recentIntents
• When A receives the join message from B, the join message is smaller than the leave message ltime. As a result, In A consul members, the state of B is always leaving.

The source code is as follows

serf/serf/serf.go

Line 1111 in 830be12

return upsertIntent(s.recentIntents, leaveMsg.Node, messageLeaveType, leaveMsg.LTime, time.Now)

serf/serf/serf.go

Line 1220 in 830be12

return upsertIntent(s.recentIntents, joinMsg.Node, messageJoinType, joinMsg.LTime, time.Now)

serf/serf/serf.go

Line 956 in 830be12

member.Status = StatusLeaving

serf/serf/serf.go

Line 1225 in 830be12

return false

/kind bug