-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Added supports for setting threadPoolProperties through @HystrixCommand annotation #326
Conversation
Hystrix-pull-requests #156 FAILURE |
The build inherited the failed test case since last pull request. The test case is inside hystrix-core, which wasn't modified in this pull request (only at hystrix-avanica). |
@dmgcodevil can you please review these changes? |
I added comments for the code lines. Ben could you please check my comments (maybe you can suggest better way)? Also I was planning add ability to annotate whole class to implement "default" properties feature. I gonna start implementation in the near future. |
…f passing ThreadPoolPropertiesSetter into the constructor
Hystrix-pull-requests #158 FAILURE |
ok I just made the change accordingly to use ConfigurationManager, and got rid of the if-else ladder. I tried locally with debugger. it works. Please review. thanks |
Thanks, looks better. Update README as well. But I still see few places for improvements, please fix them. |
…s. problem: metricsRollingStatisticalWindowInMilliseconds, and metricsRollingStatisticalWindowBuckets wouldn't be set correctly
Hystrix-pull-requests #159 FAILURE |
I did the refactoring accordingly, and added some test cases. It ended up discovering that metricsRollingStatisticalWindowInMilliseconds and metricsRollingStatisticalWindowBuckets wouldn't be set correctly. so what's the correct prefix for metrixRollingStatisticalWindow* ? Thank you. |
As I know this is property of Hystrix command:
|
Hystrix-pull-requests #160 FAILURE |
@benjchristensen I finished reviewing of this PL, could you please merge it ? Thanks. |
cool thanks. I made another pull request at branch 1.3.x: #329 |
Added supports for setting threadPoolProperties through @HystrixCommand annotation
The @HystrixCommand annotation is creating the threadPool using the default settings. we'd like to make the threadPool configurable as part of the annotation.