accumulo: Thrift frame size errors
Describe the bug Seeing error messages like the following in the manager, gc, and compaction coordinator logs:
[rpc.CustomNonBlockingServer$CustomFrameBuffer] ERROR: Read a frame size of 369295362, which is bigger than the maximum allowable frame size 16384000 for ALL connections.
[rpc.CustomNonBlockingServer$CustomFrameBuffer] ERROR: Read an invalid frame size of -2143289088. Are you using TFramedTransport on the client side?
Versions (OS, Maven, Java, and others, as appropriate):
- Affected version(s) of this project: 2.1.0-rc1
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (17 by maintainers)
Commits related to this issue
- Log the client address when FrameBuffer read or write methods return false. When FrameBuffer read and write methods return false it MAY be due to an error. Log at trace level the client address that ... — committed to dlmarion/accumulo by dlmarion 2 years ago
- Log the client address when FrameBuffer read or write methods return false (#3047) When FrameBuffer read and write methods return false it MAY be due to an error. Log at trace level the client addre... — committed to apache/accumulo by dlmarion 2 years ago
I don’t think so, as the multiplexing is at the protocol level and the frame buffer is at the transport level. Still looking…