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
Getting deserialization errors from asynchbase when enabling appends on opentsdb (2.2) #118
Comments
Pcap between opentsdb and hbase during the incident can be found here: https://docs.google.com/uc?id=0BzLBsbBPE3yoVFk3M29JSVpWZzQ&export=download |
Log from opentsdb with asynchbase debug logging enabled: https://gist.githubusercontent.com/alienth/bbdf8f8191584bbbcb00/raw/5af388c9d26c57a170b877ed4f1edf352c5c94fc/gistfile1.txt |
Existing debug logs were for an older version of asynchbase. Newest build also exhibits the same issue. I'll provide new debug logs so that the line numbers make sense. |
Exception log for latest version:
|
Thanks! And could you capture the packets around this kind of error to please? |
…action that appear after the last returned response. E.g. if the multi action had an append -> put -> append, we would throw an IOOBE and fail to properly parse the append. Thanks @alienth
that appear after the last returned response. E.g. if the multi action had an append -> put -> append, we would throw an IOOBE and fail to properly parse the append. Thanks @alienth Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>
Fixed with manolama@8db357f |
I installed opentsdb 2.2 on a preexisting 2.1 setup. 2.2 initially worked AOK, but when enabling appends I started getting the following spewed to my opentsdb.log. Discussed in the #opentsdb channel and manolama indicated this is an AsyncHBase error.
Running on hbase 1.0.0-cdh5.4.4.
The text was updated successfully, but these errors were encountered: