lidavidm commented on pull request #12442: URL: https://github.com/apache/arrow/pull/12442#issuecomment-1085818111
For the first test: that's intentional, the test is explicitly checking what happens when we use a client connected to a server that has shut down. For the second one: I get a slightly different error initially, and added some logic to also ignore that error (since during a disconnect it really doesn't matter). Afterwards, I get the same error as you. Looking in a debugger, it appears to be because the server and client side connections are being torn down at the same time, and UCX prints an error when it tries to flush data (not sure what it's trying to flush…). But for Flight, we don't care anymore, since we're disconnecting and don't expect anything. UCX offers a "force" mode to avoid this: https://openucx.github.io/ucx/api/latest/html/group___u_c_p___e_n_d_p_o_i_n_t.html#ga3be4aa93d76e41c80c780965f2f8ae57 Unfortunately, it's not suitable in my testing, because it requires setting up an error handler, and I found that doing this disables certain transports by default, most notably the shared memory transport. -- 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]
