load average goes to 80, 90 , 120 for java
Posted: Thu Jul 19, 2018 2:11 pm
Hi,
I have been running zimbra Release 8.6.0_GA_1153.RHEL7_64_20141215151110 RHEL7_64 FOSS edition for long time with 2200 users on CentOS Linux release 7.2.1511. But, today, load average increased suddenly. top command shows this.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4790 zimbra 20 0 21.829g 3.547g 22068 S 701.7 11.3 1151:20 java
this 4790 process is given below
ps aux |grep 4790
zimbra 4790 1115 11.3 22889732 3719096 ? Sl 17:43 1157:05 /opt/zimbra/java/bin/java -Dfile.encoding=UTF-8 -server -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2 -Djdk.tls.client.protocols=TLSv1,TLSv1.1,TLSv1.2 -Djava.awt.headless=true -Dsun.net.inetaddr.ttl=60 -Dorg.apache.jasper.compiler.disablejsr199=true -XX:+UseConcMarkSweepGC -XX:PermSize=128m -XX:MaxPermSize=350m -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime -XX:-OmitStackTraceInFastThrow -Xloggc:/opt/zimbra/log/gc.log -XX:-UseGCLogFileRotation -XX:NumberOfGCLogFiles=20 -XX:GCLogFileSize=4096K -Djava.net.preferIPv4Stack=true -Xss256k -Xms4096m -Xmx4096m -Xmn1638m -Djava.io.tmpdir=/opt/zimbra/mailboxd/work -Djava.library.path=/opt/zimbra/lib -Djava.endorsed.dirs=/opt/zimbra/mailboxd/common/endorsed -Dzimbra.config=/opt/zimbra/conf/localconfig.xml -Djetty.home=/opt/zimbra/mailboxd -DSTART=/opt/zimbra/mailboxd/etc/start.config -jar /opt/zimbra/mailboxd/start.jar --module=zimbra,server,servlet,servlets,jsp,jmx,resources,websocket,ext,plus,rewrite,monitor,continuation,webapp,setuid jetty.home=/opt/zimbra/mailboxd /opt/zimbra/mailboxd/etc/jetty.xml
sometimes load average goes to 80, 90 , 120 etc. it never happened before.
everything worked perfectly well until this morning.
here's bit of config settings
zmlocalconfig | grep java_heap
mailboxd_java_heap_new_size_percent = 20
mailboxd_java_heap_size = 6410
zmprov gs `zmhostname` zimbraHttpNumThreads
zimbraHttpNumThreads: 500
and
zmprov gs `zmhostname` zimbraLmtpNumThreads
zimbraLmtpNumThreads: 40
What has gone wrong? Hope to hear from you.
I have been running zimbra Release 8.6.0_GA_1153.RHEL7_64_20141215151110 RHEL7_64 FOSS edition for long time with 2200 users on CentOS Linux release 7.2.1511. But, today, load average increased suddenly. top command shows this.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4790 zimbra 20 0 21.829g 3.547g 22068 S 701.7 11.3 1151:20 java
this 4790 process is given below
ps aux |grep 4790
zimbra 4790 1115 11.3 22889732 3719096 ? Sl 17:43 1157:05 /opt/zimbra/java/bin/java -Dfile.encoding=UTF-8 -server -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2 -Djdk.tls.client.protocols=TLSv1,TLSv1.1,TLSv1.2 -Djava.awt.headless=true -Dsun.net.inetaddr.ttl=60 -Dorg.apache.jasper.compiler.disablejsr199=true -XX:+UseConcMarkSweepGC -XX:PermSize=128m -XX:MaxPermSize=350m -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime -XX:-OmitStackTraceInFastThrow -Xloggc:/opt/zimbra/log/gc.log -XX:-UseGCLogFileRotation -XX:NumberOfGCLogFiles=20 -XX:GCLogFileSize=4096K -Djava.net.preferIPv4Stack=true -Xss256k -Xms4096m -Xmx4096m -Xmn1638m -Djava.io.tmpdir=/opt/zimbra/mailboxd/work -Djava.library.path=/opt/zimbra/lib -Djava.endorsed.dirs=/opt/zimbra/mailboxd/common/endorsed -Dzimbra.config=/opt/zimbra/conf/localconfig.xml -Djetty.home=/opt/zimbra/mailboxd -DSTART=/opt/zimbra/mailboxd/etc/start.config -jar /opt/zimbra/mailboxd/start.jar --module=zimbra,server,servlet,servlets,jsp,jmx,resources,websocket,ext,plus,rewrite,monitor,continuation,webapp,setuid jetty.home=/opt/zimbra/mailboxd /opt/zimbra/mailboxd/etc/jetty.xml
sometimes load average goes to 80, 90 , 120 etc. it never happened before.
everything worked perfectly well until this morning.
here's bit of config settings
zmlocalconfig | grep java_heap
mailboxd_java_heap_new_size_percent = 20
mailboxd_java_heap_size = 6410
zmprov gs `zmhostname` zimbraHttpNumThreads
zimbraHttpNumThreads: 500
and
zmprov gs `zmhostname` zimbraLmtpNumThreads
zimbraLmtpNumThreads: 40
What has gone wrong? Hope to hear from you.