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.

Sign up for GitHub

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

Jump to bottom

DC services are not registered by default after an Eureka re-start #135

Closed
jboulon opened this issue Jun 2, 2014 · 3 comments
Closed

DC services are not registered by default after an Eureka re-start #135

jboulon opened this issue Jun 2, 2014 · 3 comments
Milestone
1.1.137

Comments

@jboulon
Copy link

jboulon commented Jun 2, 2014

When Eureka is running in a Data center and in case of Eureka re-start (even rolling upgrade). Eureka will not re-register existing services on the new Eureka node e after re-start.
For AWS instance there's some specific code in place to re-register instances from the same region but that function return false in all other cases.
@jboulon
Copy link
Author

jboulon commented Jun 2, 2014

See #134 for the fix

@NiteshKant
Copy link
Contributor

Thanks @jboulon! I have provided my comments on #134

@NiteshKant
Copy link
Contributor

The fix is done in #150 instead.

@NiteshKant NiteshKant added this to the 1.1.137 milestone Jul 22, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.1.137
Development

No branches or pull requests
2 participants
@jboulon @NiteshKant