[Bug] Incorrect shuffle server status

[xianjingfeng]

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before asking

• I have searched in the issues and found no similar issues.

Describe the bug

When i review the pr #1053, I found two problems:

1. The shuffle server status will be wrong if the server is decommissioning or decommissioned. Let's look at the following code.

incubator-uniffle/coordinator/src/main/java/org/apache/uniffle/coordinator/SimpleClusterManager.java

Lines 137 to 151 in 9b725f2

	for (ServerNode sn : servers.values()) {
	if (timestamp - sn.getTimestamp() > heartbeatTimeout) {
	LOG.warn("Heartbeat timeout detect, {} will be removed from node list.", sn);
	sn.setStatus(ServerStatus.LOST);
	lostNodes.add(sn);
	unhealthyNodes.remove(sn);
	} else if (ServerStatus.UNHEALTHY.equals(sn.getStatus())) {
	LOG.warn("Found server {} was unhealthy, will not assign it.", sn);
	unhealthyNodes.add(sn);
	lostNodes.remove(sn);
	} else {
	sn.setStatus(ServerStatus.ACTIVE);
	lostNodes.remove(sn);
	unhealthyNodes.remove(sn);
	}

2. We can't obtain decommissioning or decommissioned server list from API '/api/server/nodes'

Affects Version(s)

master

Uniffle Server Log Output

No response

Uniffle Engine Log Output

No response

Uniffle Server Configurations

No response

Uniffle Engine Configurations

No response

Additional context

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!