threads leak in thread-per-connection dispatcher plugin

Bug #1432409 reported by Vlad Lesin
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MOVED - Percona Playback

Bug Description

When thread-per-connection dispatcher plugin is used each new connection is served by separate thread. In the case if there is no information about connection termination in input file the thread which serves connection will not be finished and the number of spawned threads and mysql connections will rise. As for tcpdump plugin such situation can be when there is no FIN/RST packet in tcpdump file due to dropped packets during capturing (see ). query-log plugin does not contain the code for detecting connection finishing at all.

The fast workaround: use thread thread-pool dispatcher plugin instead of default thread-per-connection(--dispatcher-plugin=thread-pool).

The possible fixes:
1) check if it is possible to detect connection finishing in query log and implement coresponsing feature in query-log plugin (see "administrator command: Quit" in query log file)
2) set time-to-live for inactive threads in thread-per-connection dispatcher plugin

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers