0

What is the difference between eureka.instance.instance-id and eureka.instance.metadataMap.instanceId? I ran 2 instances of same service on same host (localhost) and to have a unique instanceId, I tried both eureka.instance.instance-id and eureka.instance.metadataMap.instanceId. Both properties worked fine and service instances registered successfully with eureka server.

I found below post where both the option are given

how to create multiple instances of eureka services registered into eureka service registry?

So, what is the difference between them and where should I use these properties?

sunilks23
  • 15
  • 5

1 Answers1

0

There isn't any as such. We can use both :).

When eureka server asks for instanceId while registering client here is what it gets-

@Override
public String getInstanceId() {
    if (this.instanceId == null && this.metadataMap != null) {
        return this.metadataMap.get("instanceId");
    }
    return this.instanceId;
}

So, if you set it using eureka.instance.instance-id it returns the same otherwise it tries to find the instanceId from metadata (which is set using- eureka.instance.metadataMap.instanceId).

You can check EurekaInstanceConfigBean class for more details.

Sachin
  • 521
  • 3
  • 11
  • 1
    This was useful. Just to add to where we should use eureka.instance.metadataMap.* I found in EurekaInstanceConfigBean class /** * Gets the metadata name/value pairs associated with this instance. This information * is sent to eureka server and can be used by other instances. */ private Map metadataMap = new HashMap<>(); Also, a useful blog on dynamic metadata [https://blog.codecentric.de/en/2018/01/spring-cloud-service-discovery-dynamic-metadata/](https://blog.codecentric.de/en/2018/01/spring-cloud-service-discovery-dynamic-metadata/) – sunilks23 Oct 14 '19 at 19:20