Solr plugin crashes mysql (memory full)

[bloupbloup]

I wanted to mention I had my MariaDB server crashing and restarting those last days because of the Solr plugin. I fixed it by uninstalling the plugin in the plugin manager.

-----------

Process Name mysqld
Event Time 2017-08-27 at 01:46:09 UTC
PID 1062
Process Total Virtual Memory 4234692kB
Process Anonymous Resident Set Size 884252kB
Process File Resident Set Size 0kB
Process OOM Score 228
Status Out of Memory ⚠
Memory Information
Used 1.35 GB
Available 2.34 GB
Installed 3.69 GB
Load Information 0.09 0.12 0.14
Uptime 4 days, 15 hours, 14 minutes, and 5 seconds
IOStat Information avg-cpu:  %user   %nice %system %iowait  %steal   %idle            2.38    0.09    0.45    0.71    0.00   96.37 Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn sda              47.17      2550.59        90.67 1021369614   36306348 sdb              39.66      2475.50        90.67  991298310   36306348 md127             0.00         0.02         0.04       7815      16072 md126            15.48       148.33        80.69   59397685   32310668 md125             1.25         0.01         5.12       3941    2050944
Top Processes
PID Owner CPU% Memory % Command
15627 mysql 0.29 15.31 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=ns1.xulux.nl.err --pid-file=ns1.xulux.nl.pid
9603 cpanelsolr 0.08 8.04 /usr/lib/jvm/jre-1.8.0/bin/java -server -Xms512m -Xmx512m -XX:NewRatio=3 -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 -XX:+CMSScavengeBeforeRemark -XX:PretenureSizeThreshold=64m -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=50 -XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled -XX:+ParallelRefProcEnabled -XX:-OmitStackTraceInFastThrow -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/home/cpanelsolr/server/logs/solr_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -Dsolr.log.dir=/home/cpanelsolr/server/logs -Djetty.port=8984 -DSTOP.PORT=7984 -DSTOP.KEY=solrrocks -Dhost=127.0.0.1 -Duser.timezone=UTC -Djetty.home=/home/cpanelsolr/server -Dsolr.solr.home=/home/cpanelsolr/server/solr -Dsolr.install.dir=/home/cpanelsolr -Xss256k -Dsolr.autoSoftCommit.maxTime=3000 -Dsolr.log.muteconsole -XX:OnOutOfMemoryError=/home/cpanelsolr/bin/oom_solr.sh 8984 /home/cpanelsolr/server/logs -jar start.jar --module=http
2803 named 0.04 1.74 /usr/sbin/named -u named
4559 nobody 0.09 0.76 /usr/sbin/httpd -k start
9922 root 0.01 0.75 /usr/sbin/httpd -k start
For addtional details, see the attached dmesg log dump.

Preview of “oom_dmesg.txt”
[337474.038930] Out of memory: Kill process 1062 (mysqld) score 228 or sacrifice child
[337474.039002] Killed process 1062 (mysqld) total-vm:4234692kB, anon-rss:884252kB, file-rss:0kB, shmem-rss:0kB

 

[cPanelMichael]

Hello,

The cpanel-dovecot-solr can in-fact lead to increased memory usage on a server, however you shouldn't experience service outages related to memory usage unless your system was already close to it's memory limit. Feel free to open a support ticket using the link in my signature if you'd like us to take a closer look.

Thank you.