Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hostname reused as InstanceId disallows multiple service instances on 1 host #24

Closed
danielkwinsor opened this issue Jun 27, 2013 · 1 comment
Assignees

Comments

@danielkwinsor
Copy link

Original thread is at https://groups.google.com/forum/#!topic/eureka_netflix/Rntihgo1i50

My usecase is that I'd like to have 1 service with multiple instances running on the same host. Since they are the same service, they should have the same app name. And since they are on the same host, they have the same hostname. The problem is that in a non-AWS datacenter, the instanceID is populated by the hostname. Same app name and same instanceId leads to overwriting in the service registry. I would appreciate it if the EurekaInstanceConfig interface had a getId() method that I can implement.

Thank you.

@qiangdavidliu
Copy link
Contributor

This is possible by implementing a DataCenterInfo that also implement UniqueIdentifier.

st3v added a commit to st3v/fargo that referenced this issue Sep 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants