ivakegg commented on PR #3789: URL: https://github.com/apache/accumulo/pull/3789#issuecomment-1745179354
So I guess now if a client hits the EOFException because the max message size was exceeded, then it will retry indefinitly which was one of the symptoms we were trying to avoid. Given we can now set the max size along with the max frame size this can perhaps be avoided. However that is not really a good scenario. On the flip side, not retrying on an EOFException because a network or datanode failure could also be problematic. I need to scan some running systems to see how often this happens and the implications thereof. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
