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.

Sign up for GitHub

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

Jump to bottom

HashedWheelTimeout not cleaning up #142

Open
amotamed opened this issue Jul 7, 2016 · 5 comments
Open

HashedWheelTimeout not cleaning up #142

amotamed opened this issue Jul 7, 2016 · 5 comments
Labels
bug

Comments

@amotamed
Copy link

amotamed commented Jul 7, 2016

When using asynchbase 1.7.1 with io.netty:netty:3.10.5.Final I'm seeing HashdWheelTimeouts continuously increasing. I'm running jmap, here's an example of the output:

/usr/lib/jvm/java-1.8.0/bin/jmap -histo 1870 | grep HashedWheelTimeout
53: 4392 245952 org.jboss.netty.util.HashedWheelTimer$HashedWheelTimeout

This number continuously grows until we run out of memory on the server, it's a very gradual increase, it takes weeks to take effect with 4G heap
@manolama manolama added the bug label Sep 17, 2016
@amotamed
Copy link
Author

Just a heads up, using the latest build (1.7.2), I'm still seeing this issue

@amotamed
Copy link
Author

And we're connecting to hbase-0.94.6

@amotamed
Copy link
Author

I'm still seeing this issue on 1.8.0

@amotamed
Copy link
Author

still seeing this on 1.8.1

@manolama
Copy link
Member

Hmm, are you using the RPC timeout feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@manolama @amotamed