[SCB-2136] TESTING status microservice instances are counted as latest version

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: java-chassis-1.3.0, java-chassis-1.3.1
• Fix Version/s: java-chassis-1.3.2
• Component/s: Java-Chassis
• Assignee: liubao
• Reporter: Haishi Yao
• Created: 01/Dec/20 02:10
• Updated: 10/Dec/20 01:24
• Resolved: 10/Dec/20 01:24

Description

In some cases, the new version microservice instances may be launched with TESTING status, in order that the operators can run some tests for the new instances before they actually serve.

But at present, when consumers find the new version instances, they firstly choose the new version as the latest version and secondly filter the instances by status. As a result, if the version-rule of the consumers is "latest" and the instances of the new version are all in TESTING status, the consumers will filter out all the instances.

In such cases, the expected behavior is that SDK firstly choose the greatest version number of the UP status instances as latest version, and secondly filter out the non-UP status instances.

 

TO avoid this problem, currently the version rule of consumers should be "0.0.0+"(or "0+" shortly) to choose all versions of provider instances to invoke.

Issue Links

• links to: GitHub Pull Request #2113