mysql-test-run.pl consumes all server resources almost instantly in Percona server 5.5.27

Bug #1036522 reported by Roel Van de Paar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Confirmed
Critical
Unassigned

Bug Description

Try and execute:

$ cd /percona-server/5.5 # Containing bzr branch of 5.5.27 trunk
$ ./build/build-binary.sh ..
$ cd ..; tar -xf Percona-Server-5.5.25a-rel27.1-285.Linux.x86_64.tar.xf
$ cd Percona-Server-5.5.25a-rel27.1-285.Linux.x86_64/mysql-test
$ mkdir /dev/shm/e
$ perl mysql-test-run.pl 1st

This consumes almost all server resources after a few seconds. Trying to launch another shell process gives 'Failed to fork (Resource temporarily unavailable)' on a high-end no-load freshly-restarted server. This is not the case on all these: Percona 5.5.25a, mysql 5.5.25a, mysql 5.5.27.

There is furthermore no output shown, even after some time. CTRL-C releases the resources immediately. No large memory or CPU consumption is seen while the process hangs. The OS settings on this server are increased already, so it is unclear atm which resource is being exhausted.

Fails:
- Percona-Server-5.5.27-rel28.0-288.Linux.x86_64

Does not fail:
- Percona-Server-5.5.25a-rel27.1-285.Linux.x86_64
- mysql-5.5.25a-linux2.6-x86_64
- mysql-5.5.27-linux2.6-x86_64

This also prevents RQG from working properly.

Workaround for RQG: see bug 1036506

description: updated
Changed in percona-server:
importance: Undecided → Critical
description: updated
Revision history for this message
Roel Van de Paar (roel11) wrote :

5.5.27 revision tested was 288 <email address hidden>

Revision history for this message
Roel Van de Paar (roel11) wrote :

Re-tested on 290 <email address hidden> on Fedora 17 (3.4.6-2.fc17.x86_64) running in a VM - same issue. Re-tested in same VM with 5.5.25a - works fine. Bug confirmed.

description: updated
description: updated
description: updated
Changed in percona-server:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.