AnsweredAssumed Answered

asynchbase and protobuf versions

Question asked by tc_dev on Oct 23, 2015
I solved the problem before having chance to post the error here, so simply sharing the issue/solution

If you have an application that uses both asynchbase and any custom protobuf messaging - you **must** ensure that protobuf versions match - or otherwise attempted asyncbase accesses will go into an infinite loop (and fill up the logs) trying to parse mismatched proto messages

Specifically this means that with asynchbase 1.6.0 or 1.5.0 you must use protobuf 2.5.0. Loading the latest 2.6.1 library would cause the fatal error above

Outcomes