-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Enables monitoring of multiple services on a single physical box. #574
Enables monitoring of multiple services on a single physical box. #574
Conversation
@@ -61,12 +61,14 @@ | |||
|
|||
private final EurekaClient eurekaClient; | |||
private final Expression clusterNameExpression; | |||
private final boolean combineHostPort; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use tabs.
Have you signed the contributor's agreement? |
Just signed it. My confirmation number is 141620151006073646. |
@micheal-swiggs I changed turbine recently. I thought I'd just add your changes. When I added this test to
It fails with
If you want to rework it so a test like that doesn't fail, go for it. Otherwise, you can now create your own |
I will try to rework this. So if I add this test into my branch I should be able to reproduce the error? |
You should. the |
I've added the tests and fixed them. |
@micheal-swiggs, just looking at this and realized you've made this from the M1 branch, can you do rebase to master instead? |
I will try. |
I was not able to rebase this branch. So I have created a new pull request forked from master with the changes of this pull request. |
Last November I came across this same problem and found an open issue in Turbine's project. I finally submitted a PR addressing it. The changes introduced here definitely fixed the problem but in my opinion it would make sense that the solution were on Turbine's side. Why? Because this PR only works when you have Eureka, but doesn't when using other discovery server such as Consul. What do you think? |
By setting
turbine.instanceInsertPort.default=false
andturbine.combineHostPort=true
services registered with Eureka running on the same server(ie same hostname) can be monitored with turbine. I'm not sure if this is a good way of enabling this.Another option is to change
TurbineConfiguration
to:And allow the user to inject their own
InstanceDiscovery
implementation, e.g a subclass ofEurekaInstanceDiscovery
.