Configuration method of Eureka Cluster
This article focuses on "how to configure Eureka clusters". Interested friends may wish to have a look at it. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "how to configure Eureka clusters".
Eureka standalone configuration # stand-alone configuration server: port: 7001eureka: instance: # eureka server instance name hostname: eureka01 client: # false: do not register with the registry register-with-eureka: false # false means the registry, and my duty is to maintain the service instance There is no need to retrieve the service fetch-registry: false service-url: # to set up the address lookup service and registration service that interact with Eureka Server depend on this address (stand-alone). DefaultZone: http://${eureka.instance.hostname}:${server.port}/eureka/Eureka cluster version configuration # Cluster version configuration server: port: 7001eureka: instance: # eureka server instance name hostname: eureka01 client: # false: do not register yourself with the registry register-with-eureka: false # false indicates that the server is the registry, and my duty is to maintain the service instance There is no need to retrieve the service fetch-registry: false service-url: defaultZone: http://eureka02:7002/eureka/,http://eureka03:7003/eureka/
Eureka02
Server: port: 7002eureka: instance: # eureka server instance name hostname: eureka02 client: # false: do not register with the registry register-with-eureka: false # false indicates that the server is the registry, and my duty is to maintain the service instance, and there is no need to retrieve the service fetch-registry: false service-url: defaultZone: http://eureka01:7001/eureka/,http://eureka03:7003/eureka/
Eureka03
Server: port: 7003eureka: instance: # eureka server instance name hostname: eureka03 client: # false does not register with the registry register-with-eureka: false # false indicates that the server is the registry, and my duty is to maintain the service instance, and there is no need to retrieve the service fetch-registry: false service-url: defaultZone: http://eureka01:7001/eureka/,http://eureka02:7002/eureka/ to this point I believe that you have a deeper understanding of the "Eureka cluster configuration method", might as well come to the actual operation of it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!