[progress record]:
has been claimed by aokelu
Proposed time: 2022/05/12
Discussion time:
Acceptance time:
Complete time:
[issues]:
[email]: taokelu@gmail.com
[release]:
[proposer]: taokelu
Motivation & Background
At present, the service update directly stops all, and then starts all, which is not very elegant. It is proposed to support grayscale offline mechanism based on eureka
Basic concept
Expect to achieve goals
● The old service is offline in grayscale, and the new service is launched in grayscale, which does not affect the use of users
Implementation plan
● The service adds offline interface to eureka
● Each service supports multi-port/port range selection, and supports single-machine service multi-instance survival issue link: https://github.com/apache/incubator-linkis/issues/2190
● entrance adds status monitoring
Things to Consider & Note:
● Permission problem of offline interface
● entrance status problem
Changes
Modification | Detail | |
---|---|---|
1 | Modification of maven module | |
2 | Modification of HTTP interface | |
3 | Modification of the client interface | |
4 | Modification of database table structure | |
5 | Modification of configuration item | |
6 | Modification Error code | |
7 | Modifications for Third Party Dependencies |
Compatibility, Deprecation, and Migration Plan
- What impact (if any) will there be on existing users?
- If we are changing behavior, how will we phase out the older behavior?
- If we require special migration tools, describe them here.
- When will we remove the existing behavior?