-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buffer overflow in nio exposition #83
Buffer overflow in nio exposition #83
Comments
I'm working on a fix for this. |
Update unit tests to verify the FormattedByteChannel with the Netty ChunkedNioStream. Closes instaclustr#83
Update unit tests to verify the FormattedByteChannel with the Netty ChunkedNioStream. Closes instaclustr#83
Update unit tests to verify the FormattedByteChannel with the Netty ChunkedNioStream. Closes instaclustr#83
Update unit tests to verify the FormattedByteChannel with the Netty ChunkedNioStream. Closes instaclustr#83
Your exporter is working for two weeks without any issues. |
One Cluster works and another Cluster with same Configuration does not. Exporter seems to be not reliable. |
same as by me. |
After new data (new tables) on one of the clusters (with a working exporter) the exporter now also fails with the described message above. So it seems that the error is triggered only when (much?) data is on the cluster. |
The release from edgelaborities has fixed the issue for me. (AFAIK because they just merged #84) |
Hi, so what would it take to get this merged? |
The change to the Netty ChunkedNioStream introduced a regression.
This happens because the ChunkedNioStream will not flush the buffer unless it has reached the actual chunk limit, instead it will just make another call to
ReadableByteChannel.read()
.The text was updated successfully, but these errors were encountered: