Menu
When I run Eureka on port 8761, everything works great. The config server can register to Eureka without problem. When I change eureka port to 7001, however, things stop working and I can't seem to figure out how to fix them.
The issue seems to revolve around Eureka not being able to find a peer node running at: http://localhost:8761/eureka. The exception is:
2015-07-05 08:00:47.301 ERROR 4140 --- [egister-process]
c.netflix.eureka.cluster.PeerEurekaNode : PeerEurekaNode:
http://localhost:8761/eureka/apps/: CONFIGSERVER/localhost:Register
Indeed when Eureka starts, it says: Adding replica node: http://localhost:8761/eureka/. It seems thus that somewhere the a replica node is assumed to be running at 8761.
Is there a way to disable Eureka looking for replica nodes? Or how do I control if and when and where replica should happen? I looked at the EurekaServerConfig class (http://netflix.github.io/eureka/javadoc/eureka-core/index.html) but I could not find anything that goes in this direction.
This is with Spring Cloud 1.0.2.RELEASE.
408
To disable the Eureka Discovery Client, you can set eureka. client. enabled to false .
serviceUrl. defaultZone = http://localhost:8761/eureka eureka. client.
You can use Spring Cloud's @EnableEurekaServer to stand up a registry with which other applications can communicate. This is a regular Spring Boot application with one annotation ( @EnableEurekaServer ) added to enable the service registry.
Replication with Eureka Microservices register with Eureka and then send heartbeats every 30 seconds. If the client cannot renew the heartbeat for a few times, the registration information and the renewals are replicated to all the Eureka nodes in the cluster. This mecanism is called Peer Awareness.
You have to configure eureka.client.serviceUrl.defaultZone property in application.yml file.
144
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
