-
Notifications
You must be signed in to change notification settings - Fork 107
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
GC problem #245
Comments
Performance issues #181 |
lance
added a commit
that referenced
this issue
Jan 8, 2019
Shutting down a circuit will cause it to always return a rejected promise with an `ESHUTDOWN` `Error.code` when `circuit.fire()` is called, and the Hystrix stats stop accumulating. Once a circuit has been shut down, it cannot be reset or used again. When using the `shutdown()` method on a circuit, all listeners are cleaned up internally, preventing memory leaks. Fixes: #248 Fixes: #181 Fixes: #245
lance
added a commit
that referenced
this issue
Jan 9, 2019
Shutting down a circuit will cause it to always return a rejected promise with an `ESHUTDOWN` `Error.code` when `circuit.fire()` is called, and the Hystrix stats stop accumulating. Once a circuit has been shut down, it cannot be reset or used again. When using the `shutdown()` method on a circuit, all listeners are cleaned up internally, preventing memory leaks. Fixes: #248 Fixes: #181 Fixes: #245
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Node.js Version: V8.5.0
Operating System: centos 7
Steps to Produce Error:
when i user opossum like this, i got a GC problem:
then i use jmeter to test my application,i got CPU profile like this:
The text was updated successfully, but these errors were encountered: