-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Some queries cause a StackOverflow with a large stack of async.Deferred #812
Labels
Comments
I've been seeing exactly same problems many times... |
Perhaps this is related to #823 |
We're not using salting, but maybe it's a similar bug in another place in the code? |
This one should be resolved with AsyncHBase 1.7.2 and TSDB 2.2.1. Give it a try and post a new issue if ya'll see it please. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thu Jun 16 13:26:58 GMT+200 2016 INFO OpenTSDB I/O Worker #2 tsd.HttpQuery
[id: 0xda4091e2, /10.10.52.32:33764 => /10.10.34.13:4242] HTTP /logs?json done in 10ms
Thu Jun 16 13:26:57 GMT+200 2016 ERROR AsyncHBase I/O Worker #12 async.RegionClient
Unexpected exception from downstream on [id: 0x9b8af4de, /10.10.34.13:40230 :> /10.10.34.35:60020] java.lang.StackOverflowError: null
at com.stumbleupon.async.Deferred.access$300(Deferred.java:430) ~[async-1.4.0.jar:na]
at com.stumbleupon.async.Deferred$Continue.call(Deferred.java:1366) ~[async-1.4.0.jar:na]
at com.stumbleupon.async.Deferred.doCall(Deferred.java:1278) ~[async-1.4.0.jar:na]
at com.stumbleupon.async.Deferred.runCallbacks(Deferred.java:1257) ~[async-1.4.0.jar:na]
at com.stumbleupon.async.Deferred.access$300(Deferred.java:430) ~[async-1.4.0.jar:na]
... snip ...
pastebin of logs: http://pastebin.com/asvHWetP
In my sample i sent two queries via /api/query and got an error in response. When I send only one query, I get a response with data, but the error still happens and is logged.
Version 2.2.0
Edit: I compiled the branch 'next' and the problem still occurs.
The text was updated successfully, but these errors were encountered: