如何在Eureka Server中配置处理未主动注册的被动HTTP客户端？

Alright, let's break down how to handle passive HTTP clients that can't register themselves with Eureka Server. The key here is to add them as static instances either via configuration files or dynamically using Eureka's REST API. Here's your step-by-step guide:

You can define these passive clients directly in your Eureka Server's configuration. This works great for clients with fixed addresses that don't change often.

YAML Configuration Example #

eureka:
  instance:
    hostname: localhost
  client:
    register-with-eureka: false  # Eureka Server doesn't register itself
    fetch-registry: false        # No need to fetch registry from other nodes
  server:
    enable-self-preservation: false  # Optional: Disable for testing (faster instance state updates)
    wait-time-in-ms-when-sync-empty: 0  # Optional: Speed up sync on startup
  # Define your passive clients here
  static-instances:
    my-passive-service-group:
      - instance-id: passive-client-01
        host-name: 192.168.1.100
        port: 8080
        app: MY_PASSIVE_SERVICE  # Service name other apps use to discover this client
        status: UP
        metadata-map:
          zone: us-east-1
          api-version: v1

Properties Configuration Example #

eureka.instance.hostname=localhost
eureka.client.register-with-eureka=false
eureka.client.fetch-registry=false
eureka.server.enable-self-preservation=false
eureka.server.wait-time-in-ms-when-sync-empty=0

# Static client configuration
eureka.static-instances.my-passive-service-group[0].instance-id=passive-client-01
eureka.static-instances.my-passive-service-group[0].host-name=192.168.1.100
eureka.static-instances.my-passive-service-group[0].port=8080
eureka.static-instances.my-passive-service-group[0].app=MY_PASSIVE_SERVICE
eureka.static-instances.my-passive-service-group[0].status=UP
eureka.static-instances.my-passive-service-group[0].metadata-map.zone=us-east-1
eureka.static-instances.my-passive-service-group[0].metadata-map.api-version=v1

If your passive clients have dynamic addresses or you need to add them at runtime, use Eureka's REST API to register them programmatically or via tools like curl.

Example POST Request #

curl -X POST \
  http://your-eureka-server:8761/eureka/apps/MY_PASSIVE_SERVICE \
  -H 'Content-Type: application/json' \
  -d '{
    "instance": {
      "instanceId": "passive-client-02",
      "hostName": "192.168.1.101",
      "port": {
        "$": 8081,
        "@enabled": "true"
      },
      "status": "UP",
      "metadata": {
        "zone": "us-west-1",
        "api-version": "v1"
      },
      "app": "MY_PASSIVE_SERVICE",
      "ipAddr": "192.168.1.101",
      "vipAddress": "MY_PASSIVE_SERVICE"
    }
  }'

Note: If the passive client can't send heartbeat requests to Eureka, the server will eventually mark it as DOWN. To adjust this behavior, tweak Eureka's eviction and heartbeat settings (see section 3).

• Service Name Consistency: Make sure the app value matches exactly what other services use when trying to discover this passive client. Eureka is case-sensitive here.
• Cluster Sync: If you're running a multi-node Eureka cluster, static configurations need to be added to all nodes. For dynamic registrations, Eureka will sync the instance across the cluster automatically.
• Heartbeat & Eviction Tuning: For clients that can't send heartbeats, adjust these settings to prevent premature eviction:

  eureka:
    server:
      eviction-interval-timer-in-ms: 30000  # How often Eureka checks for stale instances (default 60s)
      instance-expiration-duration-in-seconds: 180  # Time before an instance is marked DOWN (default 90s)
  

• Self-Preservation Mode: Keep enable-self-preservation: true in production. This prevents Eureka from deleting all instances if there's a network blip. Only disable it in testing environments.

内容的提问来源于stack exchange，提问作者nidi