dlmarion commented on PR #5550: URL: https://github.com/apache/accumulo/pull/5550#issuecomment-2897788934
Some observations: It appears that based on the referenced Thrift code, if the incoming frame is less than the max frame size, but reading the frame would use more memory than the total, it returns `true` (for the connection to remain alive) and does **not** read the frame off the network stack. The tcp stack has configuration knobs for setting the buffer size on the sender and receiver side, and for how much data can be in flight. I think the other question here is what happens on the Thrift sender side when the total max memory is reached on the receiver side. Does it just sit there and wait indefinitely? If the sender waits forever and does not get a timeout or other exception, then maybe there is nothing to do here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@accumulo.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
