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

HashedWheelTimer resource leak #88

Open
Looveh opened this issue Apr 6, 2016 · 0 comments
Open

HashedWheelTimer resource leak #88

Looveh opened this issue Apr 6, 2016 · 0 comments

Comments

@Looveh
Copy link

Looveh commented Apr 6, 2016

When migrating many databases (1 SQL db, 8 Cassandra keyspaces, 1 Elasticsearch cluster) with many migrations (about 30 migrations per db) I get a report of resource leaking:

Apr 06, 2016 9:49:52 AM io.netty.util.ResourceLeakDetector reportLeak
SEVERE: LEAK: You are creating too many HashedWheelTimer instances.  
HashedWheelTimer is a shared resource that must be reused across the JVM,
so that only a few instances are created.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant