Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: batch
-
Labels:None
Description
When using pipelining, a batch can hang when statement.setQueryTimout is set and batch time > to query timeout.
When query timeout is reached, a KILL QUERY command can be issued. Depending on server state, results seem to miss a result packet (reproduced on travis with galera). Connector might wait for a result that will never come.