mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-26 19:35:12 +00:00
20c258f202
The problem is that we set the session state to WAIT_COMPLETE in send_complete_message's continuation, the peer node might send COMPLETE_MESSAGE before we run the continuation, thus we set the wrong status in COMPLETE_MESSAGE's handler and will not close the session. Before: GOT STREAM_MUTATION_DONE receive task_completed SEND COMPLETE_MESSAGE to 127.0.0.2:0 GOT COMPLETE_MESSAGE, from=127.0.0.2, connecting=127.0.0.3, dst_cpu_id=0 complete: PREPARING -> WAIT_COMPLETE GOT COMPLETE_MESSAGE Reply maybe_completed: WAIT_COMPLETE -> WAIT_COMPLETE After: GOT STREAM_MUTATION_DONE receive task_completed maybe_completed: PREPARING -> WAIT_COMPLETE SEND COMPLETE_MESSAGE to 127.0.0.2:0 GOT COMPLETE_MESSAGE, from=127.0.0.2, connecting=127.0.0.3, dst_cpu_id=0 complete: WAIT_COMPLETE -> COMPLETE Session with 127.0.0.2 is complete