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

HystrixTimer when it initialize ScheduledThreadPoolExecutor does not set RemoveOnCancelPolicy for true #1998

Open
lovingcodesk opened this issue Jul 4, 2020 · 0 comments · May be fixed by #1999

Comments

@lovingcodesk
Copy link

set follow configurations for some command key:

hystrix.command.fallbackcmd.execution.isolation.thread.timeoutInMilliseconds = 1000000000
hystrix.command.fallbackcmd.execution.isolation.strategy = SEMAPHORE
hystrix.command.fallbackcmd.execution.isolation.semaphore.maxConcurrentRequests = 1000
hystrix.command.fallbackcmd.fallback.enabled = true
hystrix.command.fallbackcmd.circuitBreaker.enabled = true

when it invoke TimerReference.clear(), it does not remove this thread from the queue in ScheduledThreadPoolExecutor,In the case of a large number of requests for long time under this hystrix command key will cause memory leak ,we encounter this problem at our production environment,it Influences service performance

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