# Percona Keeps Crashing

**URL:** <https://forums.percona.com/t/percona-keeps-crashing/1647>\
**Category:** Other MySQL® Questions\
**Created:** [August 15, 2011, 9:13pm UTC](https://forums.percona.com/t/percona-keeps-crashing/1647 "2011-08-15T21:13:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![blshao](https://avatars.discourse-cdn.com/v4/letter/b/6bbea6/32.png) [@blshao](https://forums.percona.com/u/blshao)\
**Post date:** [August 15, 2011, 9:13pm UTC](https://forums.percona.com/t/percona-keeps-crashing/1647/1 "2011-08-15T21:13:27Z")

</div>

We use two percona servers as master-slave replication. The server only has a few simple tables, but each table has hundreds of millions rows and this number keeps increasing.

However, the slave crashes quite often, and I guess, because of some memory spike. The problem is as long as it crashed once, it keeps crashing: After it restarts and recovers from last crash, the slave SQL-thread stuck at opening tables when it is trying to do the replication. In this case, I have to stop the server and reset the master log position. By the way, I also use innodb\_buffer\_pool\_restore\_at\_startup = 300.

My question is: what causes the crash, the replication or the buffer pool restore, or something else?

my configuration file is listed below and the server has 16GB memory:

key\_buffer = 10M  
max\_allowed\_packet = 64M  
thread\_stack = 192K  
thread\_cache\_size = 1000  
binlog\_cache\_size = 1M  
max\_heap\_table\_size = 64M  
sort\_buffer\_size = 2M  
join\_buffer\_size = 2M  
myisam-recover = BACKUP  
max\_connections = 1000  
table\_cache = 100000  
thread\_concurrency = 8  
tmp\_table\_size = 64M  
log-bin = mysql-bin

query\_cache\_limit = 64M  
query\_cache\_size = 256M  
ft\_min\_word\_len = 4

# 

# \* Logging and Replication

# 

log\_error = /var/log/mysql/error.log

long\_query\_time = 2  
log\_slow\_queries

server-id = 2  
log-bin = mysql-bin  
relay-log = localhost-relay-bin  
expire\_logs\_days = 2  
max\_binlog\_size = 100M  
bulk\_insert\_buffer\_size = 64M

innodb\_buffer\_pool\_size = 12G  
innodb\_thread\_concurrency = 0  
innodb\_concurrency\_tickets = 5000  
innodb\_flush\_method = O\_DIRECT  
innodb\_data\_file\_path = ibdata1:1G;ibdata2:1G:autoextend  
innodb\_lock\_wait\_timeout = 100  
innodb\_locks\_unsafe\_for\_binlog = 1  
innodb\_buffer\_pool\_instances = 8  
innodb\_log\_file\_size = 256M  
innodb\_log\_buffer\_size = 8M  
innodb\_flush\_log\_at\_trx\_commit=2  
innodb\_additional\_mem\_pool\_size = 16M  
innodb\_read\_io\_threads = 8  
innodb\_write\_io\_threads = 8  
innodb\_file\_per\_table = 1  
innodb\_doublewrite = 0  
innodb\_buffer\_pool\_restore\_at\_startup = 300  
innodb\_open\_files = 500  
sync\_binlog = 0

---

<div class="post-metadata">

**Author:** ![revin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/revin/32/824_2.png) [@revin](https://forums.percona.com/u/revin)\
**Post date:** [August 30, 2011, 3:42pm UTC](https://forums.percona.com/t/percona-keeps-crashing/1647/2 "2011-08-30T15:42:14Z")

</div>

That depends, what does the error log say when the server crashes? There should be a stacktrace or an indication why it crashed.