-
Notifications
You must be signed in to change notification settings - Fork 593
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
DataStorm/reliability test hang #3309
Comments
The test eventually recover but was stuck there for a while:
Note the recovery only happen after pausing the reader and writer in the debugger to retrieve the stack traces, upon detach the debugger. This pausing and detaching might have cause the connection to get lost and the session to start a new recovery... |
The recovery happens after the connection is closed by the inactivity timeout, see long for a similar failure:
I suspect there is a race condition in the announcement of elements with established sessions, and the writer get stuck waiting for the connected readers notification. |
See another occurrence
Unfortunately this is not reported as a failure, because the session recovers after the connection is closed by the idle timeout. |
Logs and stacks from a different failure:
Reader
Writer
client-122824-1841.log |
The tests hangs, I got the same issue a mac Book pro, and Debian.
The test hanging is
running reader/writer as client with 2 nodes (reversed start order) test ]
I got this testing with fixes from #3294.
Reader:
Writer:
client-122624-1336.log
node1-122624-1336.log
node2-122624-1336.log
server-122624-1336.log
The text was updated successfully, but these errors were encountered: