Closed liuninglin closed 5 years ago
By the way, I changed the discovery server from ANS to Consul, then this issue didn't appear again.
service a build with spring boot 2.0.6.RELEASE and spring cloud Finchley, but ans and acm is 2.1.0.BUILD-SNAPSHOT version.
2.1.0.BUILD-SNAPSHOT is build on spring cloud greenwich and spring boot 2.1.x.
So you could use acm and ans of 0.2.1.RELEASE version when run service a.
Spring Cloud Release Trains:
Release Train | Boot Version |
---|---|
Greenwich | 2.1.x |
Finchley | 2.0.x |
Edgware | 1.5.x |
Dalston | 1.5.x |
refer: Spring Cloud
ANS Starter will be in maintenance mode in the future and it is recommend to use Nacos to replace it.
Next version ACM is compatible with Nacos.
@liuninglin “they always turn down after several minutes unexpectedly” , You mean your java progress turn down ? or just can't find service in edas-lite-configcenter dashboard?
@flystar32
So, all phenomena above are so weird.
@flystar32 And I really concern about that this kind of annoying issues will turn out in Ali Cloud EDAS(version serverless)
No one who is using EDAS submit this issue that Application turn down automatically, Could you please help to provide an Minimal, Complete, and Verifiable example ?
1.Browser showing error https://drive.google.com/file/d/1EEbX2-LeF3LPAkQa_Zy9qk2KXd1nfjkl/view
2.Local edas-lite-configcenter https://drive.google.com/file/d/1NA_4-VFuWCy5akBjOoanv8Rc9j161sx9/view
@liuninglin 搜索这个钉钉群号,加钉钉群 23335402
service a: spring boot: 2.0.6.RELEASE spring cloud: Finchley.SR2 acm: 2.1.0.BUILD-SNAPSHOT ans: 2.1.0.BUILD-SNAPSHOT service b: spring boot: 1.5.10.RELEASE spring cloud: Edgware.SR3 acm: 0.1.1.RELEASE ans: 0.1.1.RELEASE local edas: edas-lite-configcenter.tar.gz
Two services above which are registered in ANS(local mode), and they always turn down after several minutes unexpectedly. After that, these two services disappeared from EDAS Configuration Center(local mode) when I checked the status on my browser. Besides this, I cannot acquire any detail information for these two dead services.
So, I deeply concern that this unexpected issue will appear again in EDAS after I deploy my services on EDAS Production Environment.