[MDEV-3979] Server crashes in Index_statistics::set_avg_frequency on SELECT or INSERT Created: 2012-12-24 Updated: 2013-10-04 Resolved: 2013-10-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Igor Babaev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Built with BUILD/compile-pentium-debug-max-no-ndb
Steps to reproduceStart server on a clean datadir as
Branch or pull bzr tree lp:randgen cd randgen Download files mdev-3972.yy and mdev-3972.zz attached to the bug MDEV-3972 to the root of randgen folder Run
Notes: Important: Do not forget to replace 3306 in gentest dsn option with your server's port if you run it on a different one. Important: I could NOT reproduce the crash when I built with BUILD/compile-pentium-valgrind-max-no-ndb, although I didn't keep trying for very long. With BUILD/compile-pentium-debug-max-no-ndb it was reproducible well enough. Important: the server option disable-debug was critical, at least on my machine: I could never reproduce the crash if I skipped the option. Please use it at least at the beginning, you can experiment later after you make sure it's reproducible this way. I ran the test using this exact algorithm, data and grammar files, 6 times in a row, to collect some statistics. 4 times it crashed with the stack trace described here, and 2 times it was The test as configured above runs with 8 connections. Functionally, it's excessive, on a Windows machine I was able to get the crash with 4 connections. But on my Ubuntu installation, it required more. If you are getting the crash fast enough, you can try to reduce the number in the threads parameter, if it helps to debug. If you start the test again after crash, it's better to re-create the datadir. I've seen cases when stat tables were reported corrupted after a crash, and the server would crash again almost immediately, I suppose it can be misleading for debugging the underlying problem. I could not reproduce the problem on a slow 32-bit machine. I'm not sure whether it's because it's 32-bit or because it's slow, but please keep it in mind. |
| Comments |
| Comment by Elena Stepanova [ 2012-12-26 ] |
|
The instruction for reproducing the issue is now finalized (at least that's all I have at the moment, and it works reliably for me). |