I have configured eureka-server as a client with configuration specified below.
I am trying to rename the service to 'eureka-registry' (originally configured as 'eureka-server'). I have deleted the ecs service from AWS to avoid peer lookup. Have modified below configuration to reflect new name. However when the new service comes up it tries to find 'eureka-server' (old server) and fills logs completely with trying to locate the peer. Please suggest what I am missing or how to handle it.
Comment From: OlgaMaciaszek
Hello, @vishakhakadam09. Please learn how to properly format code and logs. If I understand correctly what you are trying to do, setting service-url might be what you're looking for. You can do it like so:
eureka:
client:
service-url:
defaultZone: https://dev.eureka-registry.rd.xxx.io/eureka/
Let me know if this is helpful.
Comment From: vishakhakadam09
@OlgaMaciaszek Sorry for improper format. I have updated my post with correct format. It looks like workflow-registry is trying to poll for previous eureka server i.e. eureka-service.rd.xxx.io. Could you please suggest what needs to be done in order to avoid it and not look for older instance.
Comment From: OlgaMaciaszek
Yes, it does seem so. Setting the zone as shown here should work. If it still persists, I will need a sample to verify why. Please provide a minimal, complete, verifiable example that reproduces the issue.
Comment From: spring-cloud-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-cloud-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.