-
-
Notifications
You must be signed in to change notification settings - Fork 936
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
POST -> Premature close? #1556
Comments
Can you please provide the actual stack trace and not raw logs from your application? |
Can you please use native Node.js HTTP server instead of fastify? Your example is strictly tied to Unless you can provide an actual reproducible code, there is nothing we can help with. |
Thanks -- will do on both accounts |
Slowly getting there. An update on the interplay @ fastify/fastify#2739 . There seems to be something about eos stream <> compression that got times out on and fastify reports back. Still whittling down to a repro. |
Heads up! Have you figured out what part in your code is responsible for the fail? |
I think we're good to close. We got it sorted to a few things from upgrades to our web networking stack. May be of interest, e.g., docs:
const writer = new RecordBatchStreamWriter({autodestroy: true});
const writerStream = writer._getNodeStream();
const responseFut = ourGotWrapper(sessionId, {retry: 0, timeout: 5455, body: writerStream});
writer.writeAll(table);
const response = await responseFut; We'll be watching activity over the next month. Two things still bug us:
|
Describe the bug
We aren't really sure where to start on this one, including with a tighter reproduction, so any pointers on how to proceed / what it might be would be appreciated.
We suspect it is somehow in how we're connecting
got
<>fastify
over a stream, and while we finally got it reproducible, currently on a large test + deep in our app.Some clues:
This seems to appear for bigger buffers, vs smaller, but unclear. Normally I wouldn't file this coarse of an issue, but it's a weird one for us to dig into.
On the fastify side, the closest related we saw is Sporadic ERR_STREAM_PREMATURE_CLOSE fastify/fastify-static#116
We've had to iterate with
eos
handling this year as that has been changing in various engine/libs, though not in the last ~2 monthsActual behavior
See trace on below
got
request, including auto-retry also failing (deterministic re-fail is promising..):=>
And on the fastify service side, we're going through https://github.com/apache/arrow/blob/fbb781bcdd15d54c52c71881c5c53d0c68069be6/js/src/ipc/reader.ts#L521 :
=>
=> Session logs:
Checklist
The text was updated successfully, but these errors were encountered: