instance ip 匹配

[McdullFei]

Fixes #2226

针对次bug做的一次fix
#2226

[TeslaCN]

Could you add unit tests for your changes?

[songxiaosheng]

LGTM

[linghengqian]

• Can you change the commit content to English? This will help others search.

[linghengqian]

• Do you still have time to update the current PR? Maybe allow another person to raise a new PR fixing the current one?

[Copilot]

Pull Request Overview

This PR fixes an issue with instance IP matching by improving the comparison logic from a prefix-based match to an exact match after extracting the IP portion from the instance identifier.

• Changes IP matching logic from startsWith() to exact equality comparison
• Extracts IP address from instance identifier using string split operation

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The code assumes the instance identifier always contains '@-@' delimiter, but if it doesn't, split() will return the original string. This could cause issues if the instance format is different. Consider adding validation or using a more robust parsing approach.

Suggested change

	for (String each : jobNodeStorage.getJobNodeChildrenKeys(InstanceNode.ROOT)) {
	for (String each : jobNodeStorage.getJobNodeChildrenKeys(InstanceNode.ROOT)) {
	if (!each.contains("@-@")) {
	// Skip malformed instance identifier
	continue;
	}

[Copilot]

If the ip parameter is null, this will cause a NullPointerException. Consider using Objects.equals(eachIp, ip) or add null check for the ip parameter.