A Warning About Apache Thrift's Asynchronous Clients

By default if you use the asynchronous client for thrift it will be using a FRAMED transport layer, even though there is no mention of this in the code / docs.

You’ll know this is happening because your server will give you the following error message when it receives an rpc:

org.apache.thrift.protocol.TProtocolException: Missing version in readMessageBegin, old client?

If you have no control over the server code (eg, if you’re using flume), then you’ll have to fall back to the synchronous client, sorry.

Matthew Rathbone's Picture

Matthew Rathbone

CEO of Beekeeper Data. British. Data Nerd. Lucky husband and father. More about me

Need More Hadoop Reading?

I've collected a list of the top Hadoop books on the market

Join the discussion

comments powered by Disqus