*Solr prod stopped yesterday. How to prevent this.*

Solr heap info is :  -Xms20g -Xmx20g
JVM Heap info. : -Xms528m -Xmx8g
Physical Ram - 32GB
Solr version - 6.6.1
Swap memory - 8g

*hc_err_pid.log got created with following info in it:*
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 16106127360 bytes for
committing reserved memory.
# Possible reasons:
#   The system is out of physical RAM or swap space
#   The process is running with CompressedOops enabled, and the Java Heap
may be blocking the growth of the native heap
# Possible solutions:
#   Reduce memory load on the system
#   Increase physical memory or swap space
#   Check if swap backing store is full
#   Decrease Java heap size (-Xmx/-Xms)
#   Decrease number of Java threads
#   Decrease Java thread stack sizes (-Xss)
#   Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
#  Out of Memory Error (os_linux.cpp:2749), pid=86291,
tid=0x00007f8822e47700
#
# JRE version:  (8.0_211-b12) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.211-b12 mixed mode
linux-amd64 compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core
dumping, try "ulimit -c unlimited" before starting Java again
#


*solr_gc.log shows following:*
2019-10-23T01:24:23.688+0530: 644433.457: Total time for which application
threads were stopped: 0.0028257 seconds, Stopping threads took: 0.0016863
seconds
Heap
 par new generation   total 4369088K, used 736363K [0x00000002c0000000,
0x0000000400000000, 0x0000000400000000)
  eden space 3495296K,  13% used [0x00000002c0000000, 0x00000002dc9d5ed8,
0x0000000395560000)
  from space 873792K,  30% used [0x00000003caab0000, 0x00000003daff4d80,
0x0000000400000000)
  to   space 873792K,   0% used [0x0000000395560000, 0x0000000395560000,
0x00000003caab0000)
 concurrent mark-sweep generation total 15728640K, used 3807001K
[0x0000000400000000, 0x00000007c0000000, 0x00000007c0000000)
 Metaspace       used 45325K, capacity 47047K, committed 47324K, reserved
1091584K
  class space    used 4821K, capacity 5230K, committed 5340K, reserved
1048576K

Reply via email to