MySQL persistent queue mishandles re-connection
Bug #1319506 reported by
Berend Ozceri
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gearman |
New
|
Undecided
|
Unassigned |
Bug Description
It appears that if the connection between the job server and the MySQL server providing the persistent queue storage is severed (for example, due to the MySQL server being restarted), the job server does not appear to make any re-connection attempts. From that point on, a lot of "mysql_stmt_execute failed: Incorrect arguments to mysqld_
summary: |
- MySQL persistent queue doesn't re-connect + MySQL persistent queue mishandles re-connection |
To post a comment you must log in.
The issue may be that while the MySQL queue plugin does this:
mysql_options( queue-> con, MYSQL_OPT_ RECONNECT, &my_true);
the MySQL documentation documents that:
"...if a reconnection does occur, several aspects of the connection state are reset on the server side and your application will not be notified.
The connection-related state is affected as follows:
...
- Prepared statements are released."
and the MySQL queue plugin may be continuing to use prepared statements across re-connection conditions.