Shulou(Shulou.com)06/03 Report--

Eureka instance

A service, such as an order system, deploys multiple servers, and the service provided on each server is the instance; load configuration.

Eureka service

Refers to a service that provides a specific function, such as an order system, while the same service can provide multiple instance

Eureka client

Mainly register their own services with the service center. But it can be either a service provider or a consumer. It feels similar to Eureka instance, but the meaning is different. Eureka client is compared to Eureka server. Eureka instance is more inclined to load technology.

Eureka server

Service registry. And manage the center of each service.

Eureka instance configuration items:

# the hostname of the service registry instance eureka.instance.hostname=localhost# is registered in the Eureka service, the application group name eureka.instance.app-group-name=# is registered in the Eureka service, the application name eureka.instance.appname=# in the Eureka service, the instance is registered to the unique IDeureka.instance.instance-id=# of the service center, the IP address of the instance eureka.instance.ip-address=# the instance Compared to whether hostname gives priority to using the group name associated with this instance used by IPeureka.instance.prefer-ip-address=false# for automatic extension of the AWS platform, the default address resolution order of eureka.instance.data-center-info=# in the data center where eureka.instance.a-s-g-name=# deploys this instance is eureka.instance.default-address-resolution-order=#. The instance's environment configuration eureka.instance.environment=# initializes the instance. The initial state of registration to the service center eureka.instance.initial-status=up# indicates whether to communicate eureka.instance.instance-enabled-onit=false# the namespace of the service instance immediately as soon as the instance is registered to the service center, which is used to find the attribute eureka.instance.namespace=eureka# the child definition metadata of the service instance Can be accepted by the service center eureka.instance.metadata-map.test = test# service center delete this service instance waiting time (in seconds), the interval is the last time the service center received the heartbeat time eureka.instance.lease-expiration-duration-in-seconds=90# the instance sent the heartbeat to the service center interval, used to indicate that the service instance is available eureka.instance.lease-renewal-interval-in-seconds=30# the instance Registration service center Default number of eureka.instance.registry.default-open-for-traffic-count=1# open communications per minute eureka.instance.registry.expected-number-of-renews-per-min=1# the instance health check url, absolute path eureka.instance.health-check-url=# the instance health check url, relative path eureka.instance.health-check-url-path=/health# the instance home page url, absolute path eureka.instance.home-page-url=# the instance home page url Relative path eureka.instance.home-page-url-path=/# the security and health check url of this instance Absolute path eureka.instance.secure-health-check-url=#https communication port eureka.instance.secure-port=443#https communication port enabled eureka.instance.secure-port-enabled=false#http communication port eureka.instance.non-secure-port=80#http communication port enabled eureka.instance.non-secure-port-enabled=true# secure virtual host name (https) eureka.instance.secure-virtual-host-name=unknown# of the instance virtual host name of the instance Say (http) eureka.instance.virtual-host-name=unknown# the status of the instance presents url Absolute path eureka.instance.status-page-url=# the status of the instance presents url, and the relative path eureka.instance.status-page-url-path=/status

Eureka client configuration

# whether the client can use eureka.client.enabled=true# instances to register its own information on the eureka server for other services to discover. The default is whether this client obtains the registration information on the eureka server registry. The default is whether trueeureka.client.fetch-registry=false# is filtered out. Non-UP instances. The default is the idle waiting time after trueeureka.client.filter-only-up-instances=true# communicates with Eureka registry zone and url address eureka.client.serviceUrl.defaultZone= http://${eureka.instance.hostname}:${server.port}/eureka/#client connects to the Eureka server, and defaults to 30 seconds of eureka.client.eureka-connection-idle-timeout-seconds=30#client connection eureka server timeout The default is the read timeout of 5 seconds from eureka.client.eureka-server-connect-timeout-seconds=5#client to the server, the total number of eureka.client.eureka-server-read-timeout-seconds=8#client connections to the all eureka server, the number of stand-alone connections to the eureka server by default, and the related attributes of exponential rollback refresh of the program executed by default 50eureka.client.eureka-server-total-connections-per-host=50#. Is the maximum multiple of the retry delay. It defaults to the size of the 10eureka.client.cache-refresh-executor-exponential-back-off-bound=10# executor cache refresh thread pool, defaults to the attribute related to 5eureka.client.cache-refresh-executor-thread-pool-size=2# heartbeat executor fallback, and is the maximum multiple of the retry delay. Default is the size of the 10eureka.client.heartbeat-executor-exponential-back-off-bound=10# heartbeat executor thread pool, the frequency (s) at which 5eureka.client.heartbeat-executor-thread-pool-size=5# asks for changes in Eureka service url information, and the default time (s) for eureka.client.eureka-service-url-poll-interval-seconds=300# to initially copy instance information to the eureka server in 300 seconds. The default is 40 seconds for eureka.client.initial-instance-info-replication-interval-seconds=40# to copy instance information to eureka server again, 30 seconds for eureka.client.instance-info-replication-interval-seconds=30# to obtain registration information from eureka server registry (s), and 30 seconds for eureka.client.registry-fetch-interval-seconds=30# to obtain the region where the instance is located. The default is whether the us-east-1eureka.client.region=us-east-1# instance uses the eureka server in the same zone, and the default is true. Ideally, the eureka client and server obtain the list of availability regions under the same zone by eureka.client.prefer-same-zone-eureka=true#, separated by commas. (AWS) A comma-separated list of regions in the eureka.client.availability-zones.china=defaultZone,defaultZone1,defaultZone2#eureka service registry information. If these regions are not returned in this way, the client startup will make an error. The default is whether the nulleureka.client.fetch-remote-regions-registry=# server can redirect client requests to the backup server. If set to false, the server will process the request directly, and if set to true, it may send HTTP redirection to the client. The default is whether the falseeureka.client.allow-redirects=false# client data receive eureka.client.client-data-accept=# incremental information can be provided to the client. The default is the replacement string that gets the "_" symbol in the information serialized / deserialized by the falseeureka.client.disable-delta=false#eureka server. The default is to get the replacement string of the "$" symbol from the information serialized / deserialized by the "_" eureka.client.escape-char-replacement=__#eureka server. The default is "_ -" eureka.client.dollar-replacement= "_ -" # whether the compression of the information obtained from the server is supported when the server supports compression. The default is whether trueeureka.client.g-zip-content=true# records the differences in registry information between the eureka server and the client. By default, if falseeureka.client.log-delta-diff=false# is set to true, the client's status update will be updated on demand to the remote server, and the default is trueeureka.client.on-demand-update-status-change=true#. This client is only interested in a single VIP registry. The default is whether nulleureka.client.registry-refresh-single-vip-address=#client forcibly registers to the service center during initialization. By default, it defaults to whether the logout service displayed by falseeureka.client.should-enforce-registration-at-init=false#client in shutdown is from the service center. By default, it is the proxy host for trueeureka.client.should-unregister-on-shutdown=true# to obtain eureka service, and the default is nulleureka.client.proxy-host=# to obtain the proxy password for eureka service. The default is nulleureka.client.proxy-password=# to get the proxy port of the eureka service, the default is nulleureka.client.proxy-port=# to obtain the proxy user name of the eureka service, and the default is the nulleureka.client.proxy-user-name=# attribute interpreter eureka.client.property-resolver=# to obtain the implementation name eureka.client.backup-registry-impl=# that implements the eureka client to read the registry information when it is started for the first time as a fallback option. This is a brief × × configuration. If the latest × × × is stable, it can be removed. The default is nulleureka.client.decoder-name=#, which is a temporary encoder configuration. If the latest encoder is stable, it can be removed. The default is whether nulleureka.client.encoder-name=# uses the DNS mechanism to obtain the service list and then communicate. The default is falseeureka.client.use-dns-for-fetching-service-urls=false# to get the DNS name to query to get the eureka server, this configuration is only used if the eureka server ip address list is in DNS. The default is nulleureka.client.eureka-server-d-n-s-name=# to get the port of the eureka server, which is used only if the eureka server ip address list is in DNS. The default is nulleureka.client.eureka-server-port=#, which indicates the path of the eureka registry, or http://x.x.x.x:x/eureka/ if configured as eureka. Adding this configuration in the configuration file of eureka means that eureka registers with the registry as a client, thus forming an eureka cluster. This configuration is only used if the eureka server ip address list is in DNS. The default is nulleureka.client.eureka-server-u-r-l-context=.

Eureka Server configuration

# server configuration associated with client # 3 enable self-protection mode on the server side. No matter what the situation, the server will maintain a certain number of services. Avoid network problems with client and server, and a large number of services are cleared. Eureka.server.enable-self-preservation=true# starts the scheduled task to clear invalid services, time interval. How long is the default interval of 1 minute eureka.server.eviction-interval-timer-in-ms= 6000 minutes to clear expired delta data eureka.server.delta-retention-timer-interval-in-ms=0# expired data Whether it is also provided to the clienteureka.server.disable-delta=false#eureka server whether to record the identity of the client, whether the headereureka.server.log-identity-headers=true# request frequency limiter eureka.server.rate-limiter-burst-size=10# opens the request frequency limiter, the average value of the eureka.server.rate-limiter-enabled=false# request frequency, whether the eureka.server.rate-limiter-full-fetch-average-rate=100# imposes frequency request restrictions on the standard client. In the case of false, only the average frequency of requests for non-standard client to restrict eureka.server.rate-limiter-throttle-standard-clients=false# registration service and pull service list data eureka.server.rate-limiter-registry-fetch-average-rate=500# sets the percentage of trusted client listeureka.server.rate-limiter-privileged-clients=# in the set time range class that is expected to renew with client. How long does eureka.server.renewal-percent-threshold=0.85# update the renewal threshold eureka.server.renewal-threshold-update-interval-ms=0# for cached registration data, how long does eureka.server.response-cache-auto-expiration-in-seconds=180# update the service registration data in the cache eureka.server.response-cache-update-interval-ms=0# caches incremental data In order not to lose information during retrieval eureka.server.retention-time-in-m-s-in-delta-queue=0# when the timestamp is inconsistent, whether to synchronize eureka.server.sync-when-timestamp-differs=true# with read-only cache policy, read-only policy will not expire for cached data. Configuration of eureka.server.use-read-only-response-cache=true#server Custom implementation # implementation of 33#json conversion Class name eureka.server.json-codec-name=#PropertyResolvereureka.server.property-resolver=#eureka server xml codec implementation name eureka.server.xml-codec-name=# # configuration associated with server node and node # 3 whether sending replication data is in request Always compressing the eureka.server.enable-replicated-request-compression=false# indicates whether replication between cluster nodes should be batch processed to improve network efficiency. The maximum number of replication events allowed by eureka.server.batch-replication=false# to back up to the backup pool. This backup pool is responsible for events other than status updates. Can be based on memory size, timeout and replication traffic To set the maximum number of replication events that eureka.server.max-elements-in-peer-replication-pool=10000# allows to back up to the stateful backup pool eureka.server.max-elements-in-status-replication-pool=10000# maximum idle time of multiple service centers synchronizing information threads eureka.server.max-idle-thread-age-in-minutes-for-peer-replication=15# maximum idle time of stateful synchronization threads eureka.server.max -the maximum number of threads for each instance to replicate data in the idle-thread-in-minutes-age-for-status-replication=15# service registry, the maximum number of threads for each instance to replicate status data, the communication time for replicating data between eureka.server.max-threads-for-status-replication=1#instance and the minimum number of peer-to-peer service instance with normal eureka.server.max-time-for-replication=30000#. -1 indicates that the service center is a single node. The minimum number of threads opened between eureka.server.min-available-instances-for-peer-replication=-1#instance for state replication, the minimum number of threads opened between eureka.server.min-threads-for-status-replication=1#instance and the number of retries that can be retried when replicating data between eureka.server.number-of-replication-retries=5#eureka nodes. The default is 10 minutes. The interval between mutual updates of the eureka.server.peer-eureka-nodes-update-interval-ms=600000#eureka service status. Eureka.server.peer-eureka-status-refresh-time-interval-ms=0#eureka Peer Node connection timeout eureka.server.peer-node-connect-timeout-ms=200#eureka Idle time after Peer Node connection read data connection timeout between eureka.server.peer-node-connection-idle-timeout-seconds=30# nodes the total maximum number of eureka.server.peer- of connections between eureka.server.peer-node-read-timeout-ms=200#eureka server nodes Maximum number of stand-alone connections between node-total-connections=1000#eureka server nodes eureka.server.peer-node-total-connections-per-host=10# when the service node starts The number of times eureka attempts to obtain registration information eureka.server.registry-sync-retries=# when the service node starts, the interval between eureka attempts to obtain registration information eureka.server.registry-sync-retry-wait-ms=# when eureka server starts, how long should it wait if the instance registration information cannot be obtained from the peer node. Configuration # 3 expired data associated with eureka.server.wait-time-in-ms-when-sync-empty=0#server and remote The old behavior (if configured) that is also provided to applications that the remote regioneureka.server.disable-delta-for-remote-regions=false# rollback to the remote zone will be disabled if there is no instance of the application in the local zone. Eureka.server.disable-transparent-fallback-to-other-region=false# indicates whether the content obtained from the Eureka server must be compressed for the remote zone if the server supports it. Connection timeout for eureka.server.g-zip-content-from-remote-region=true# connection eureka remote note eureka.server.remote-region-connect-timeout-ms=1000#remote region application whitelist eureka.server.remote-region-app-whitelist.# connection eureka remote note connection idle time eureka.server.remote-region-connection-idle-timeout-seconds=30# execute remote region request thread pool size for registration information eureka.server.remote-region-fetch-thread- Pool-size=20#remote region timeout for reading data from peer eureka add points eureka.server.remote-region-read-timeout-ms=1000# gets registration information from remote region total number of connections to eureka.server.remote-region-registry-fetch-interval=30#remote region connections eureka nodes eureka.server.remote-region-total-connections=1000#remote region connections to eureka nodes number of stand-alone connections eureka.server.remote-region-total-connections-per-host=50#remote region crawls registration information storage file This reliable storage file requires a fully qualified name to specify the password of the file stored by eureka.server.remote-region-trust-store=#remote region eureka.server.remote-region-trust-store-password=#remote region url. Multiple commas separate eureka.server.remote-region-urls=#remote region url. Multiple commas separate the expiration time of the configuration # 3 cache ASG information associated with eureka.server.remote-region-urls-with-name.#server and ASG/AWS/EIP/route52. Timeout of eureka.server.a-s-g-cache-expiry-timeout-ms=0# query ASG information frequency of eureka.server.a-s-g-query-timeout-ms=300# service update ASG information eureka.server.a-s-g-update-interval-ms=0#AWS access IDeureka.server.a-w-s-access-id=#AWS security key eureka.server.a-w-s-secret-key=#AWS binding policy eureka.server.binding-strategy=eip# The name of the role that automatically extends the grouping is described from a third-party AWS account. The number of times that eureka.server.list-auto-scaling-groups-role-name=# should establish a connection to guide the eureka.server.prime-aws-replica-connections=true# server to try to bind the candidate EIP, the time interval between the eureka.server.e-i-p-bind-rebind-retries=3# server binding EIP. Check if binding; re-bind if binding fails. The interval between binding EIP on the eureka.server.e-i-p-binding-retry-interval-ms=10# server if and only if it has been bound. If and only if the service is bound, the number of eureka.server.e-i-p-binding-retry-interval-ms-when-unbound=# server attempts to bind route53 how often does the eureka.server.route53-bind-rebind-retries=3# server attempt to bind route53eureka.server.route53-binding-retry-interval-ms=30#eureka.server.route53-domain-t-t-l=10

Reference documentation:

Http://cloud.spring.io/spring-cloud-static/spring-cloud-netflix/2.0.0.RC1/single/spring-cloud-netflix.html

Https://blog.csdn.net/sunhuiliang85/article/details/76222517

Https://blog.csdn.net/zhxdick/article/details/79153711

Https://stackoverflow.com/questions/36557646/what-is-eureka-service-eureka-client-eureka-instance-and-eureka-server

Https://www.cnblogs.com/fangfuhai/p/7070325.html

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.