Align buffer overflow erros with sync producer #489
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now both producer emit buffer overflow with a message for consistency.
I investigated some buffer overflow issues on production, and first thought that the issue was to do with the
max_buffer_sizeandmax_buffer_bytesizesettings. But the error did not include information which limit we had reached. I planned on adding a message to the exception which limit was reached, then realized that the synchronous producer already did this. Only then did I discover themax_queue_sizesetting and noticed thatBufferOverflowwas raised without a message if that limit was reached. I found the corresponding error message in the logs, so now I know that this was the problem, but I think it would be good to have both error cases handled in the same way.