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

Question about turbine version. #1629

Closed
eacdy opened this issue Jan 18, 2017 · 14 comments
Closed

Question about turbine version. #1629

eacdy opened this issue Jan 18, 2017 · 14 comments
Labels

Comments

@eacdy
Copy link
Contributor

eacdy commented Jan 18, 2017

I use Spring Cloud Camden SR4 and I find that the version of tuebine in these dependencies are different.

  • spring-cloud-starter-turbine uses turbine-core-1.0.0
<dependency>
  <groupId>org.springframework.cloud</groupId>
  <artifactId>spring-cloud-starter-turbine</artifactId>
</dependency>
  • spring-cloud-starter-turbine-stream uses turbine-2.0.0-DP.2
<dependency>
  <groupId>org.springframework.cloud</groupId>
  <artifactId>spring-cloud-starter-turbine-stream</artifactId>
</dependency>

Is it a bug? OR is there any thought storm?

@ryanjbaxter
Copy link
Contributor

Are different from what? You say you are using Camden.SR4, what are you comparing it against?

@spencergibb
Copy link
Member

Those are the correct versions. Unsure what "OR is there any thought storm?" means.

@eacdy
Copy link
Contributor Author

eacdy commented Jan 19, 2017

@ryanjbaxter @spencergibb
I mean spring-cloud-starter-turbine 1.2.4 uses turbine-1.0.0, spring-cloud-starter-turbine-stream 1.2.4 uses turbine-2.0.0-DP2.
LIKE THIS.
turbine

@spencergibb
Copy link
Member

Those are the correct versions

It's on purpose.

@tjuchniewicz
Copy link
Contributor

tjuchniewicz commented Oct 25, 2017

So this is a bug! Please see differences between Turbine 1.0 and 2.0.
See: Netflix/Turbine#100, #1113, #2387

@tjuchniewicz
Copy link
Contributor

We need to align Turbine version in both poms or introduce switch in dashboard to select Turbine version backend.

@login2014
Copy link

what is the mean "introduce switch in dashboard to select Turbine version backend."?how can I do? Could you cut the picture or show me the url?I'm a newbie.

@tjuchniewicz
Copy link
Contributor

@login2014 There is no such feature for now.

@taasjord
Copy link

We are having trouble now with the wrong TPS calculation from Turbine stream. Is the situation in Spring Cloud that there is turbine version 1.0 but a dashboard that is only compatible with turbine 2?

It seems Netflix has basically abandoned the Hystrix Dashboard and it is now moved to https://github.com/Netflix-Skunkworks/hystrix-dashboard. There is a pull request there: Netflix-Skunkworks/hystrix-dashboard#6, that looks like will fix the issue.

@tjuchniewicz
Copy link
Contributor

Hi @taasjord .

This is little bit more complicated. After this change: Netflix/Hystrix#1251, copied also do Spring Cloud Netflix, Dashboard does not work correctly with both versions. In details:

Dashboard Feature Turbine 1.0 Turbine 2.0
Command Charts WRONG VALUES OK
Thread pools OK WRONG VALUES

We should wait for Netflix-Skunkworks/hystrix-dashboard#6 to be integrated and integrate this into Spring Cloud Netflix. This will fix issue for Turbine 1.0 only.

@spencergibb
Copy link
Member

We don't need to wait since we forked the dashboard. We should provide an option or parameter depending on which version of turbine is used

@tjuchniewicz
Copy link
Contributor

Right. To quickly make Dashboard compatible with Turbine 1.0 we can revert #2388 and create new ticket to make it compatible with Turbine 2.0.

@taasjord
Copy link

taasjord commented May 12, 2018

If anyone else needs to fix it themselves, I simply applied the change in Netflix-Skunkworks/hystrix-dashboard#6 (a revert of #2388) on a hystrixCommand.js copied from Spring Cloud source into the same path in static folder of my @EnableHystrixDashboard application, and it did work for me. It is now showing correct requests per second.

@spring-projects-issues
Copy link

Closing due to age of the question. If you would like us to look at this issue, please comment and we will look at re-opening the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants