You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after #32809, when a conn receives a kill signal, it can skip out of the blocked read of client cmd and check the kill signal, and quit. This has a pre-condition that you have done the last cmd your received (meaning dispatch and writing result work is done)
for {
+-> 1: cmd, err = readPackage (currently can skip out when timeout)
| ... (kill signal check)
| 2: dispatch(cmd).
| ...
| 3: drain result (chunk unit)
| 1: Next (check kill signal in every operator's Next function)
| 2: Write results to conn (still blocked write)
+----+
...
But if we blocked at step 3-2 (writing result) in the last cmd you just received, the kill signal is impossible to be checked even if you have the read cmd timeout.
2. What did you expect to see? (Required)
kill statement should be responded quickly anyway
3. What did you see instead (Required)
block at writeResult to conn
4. What is your TiDB version? (Required)
even master
The text was updated successfully, but these errors were encountered:
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
after #32809, when a conn receives a kill signal, it can skip out of the blocked read of client cmd and check the kill signal, and quit. This has a pre-condition that you have done the last cmd your received (meaning dispatch and writing result work is done)
But if we blocked at step 3-2 (writing result) in the last cmd you just received, the kill signal is impossible to be checked even if you have the read cmd timeout.
2. What did you expect to see? (Required)
kill statement should be responded quickly anyway
3. What did you see instead (Required)
block at writeResult to conn
4. What is your TiDB version? (Required)
even master
The text was updated successfully, but these errors were encountered: