[
https://issues.apache.org/jira/browse/SOLR-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15874799#comment-15874799
]
Shawn Heisey commented on SOLR-10172:
-
It does indeed look like a duplicate of SOLR-10130. This is a problem that
only affects 6.4.0 and 6.4.1.
Your problem statement says version 6.0 ... but then in the details, the
directory path contains "6.4.1" ... these are *VERY* different versions. There
are six releases and ten months between these versions.
> Sorl 6 with jetty issues
>
>
> Key: SOLR-10172
> URL: https://issues.apache.org/jira/browse/SOLR-10172
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Abc
>Priority: Blocker
>
> Issues with solr settings while migrating from solr 4.0 to solr6.0.
> Issue Faced : My cpu consumption goes to unacceptable levels. ie. load on
> solr4.0 is between 6 to 10 while load on solr 6 reaches 100 and since its the
> production i rolled back quickly.
> My Solr4 setting
> - Running on tomcat
> - JVM Memory : 16GB
> - 24 core cpu
> - JVM settings :
>- JVM Runtime Java HotSpot(TM) 64-Bit Server VM (24.45-b08)
>- Processors 24
>- Args : Paths mentioned here
> **My Solr6 setting**
> - Running on jetty
> - JVM Memory : 20GB
> - 32 core cpu
> - JVM settings :
>- Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 1.8.0_45 25.45-b02
>- Processors 32
>- Args
> - DSTOP.KEY=solrrocks
> - DSTOP.PORT=7983
> - Djetty.home=/usr/local/solr-6.4.1/server-Djetty.port=8983
> -
> Dlog4j.configuration=file:/usr/local/solr-6.4.1/example/resources/log4j.properties
> -
> Dsolr.install.dir=/usr/local/solr-6.4.1-Dsolr.log.dir=/usr/local/solr-6.4.1/example/techproducts/solr/../logs
> - Dsolr.log.muteconsole
> -
> Dsolr.solr.home=/usr/local/solr-6.4.1/example/techproducts/solr-Duser.timezone=US/Eastern
> - XX:+AggressiveOpts
> - XX:+CMSParallelRemarkEnabled
> - XX:+CMSScavengeBeforeRemark
> - XX:+ParallelRefProcEnabled
> - XX:+PrintGCApplicationStoppedTime
> - XX:+PrintGCDateStamps
> - XX:+PrintGCDetails
> - XX:+PrintGCTimeStamps
> - XX:+PrintHeapAtGC
> - XX:+PrintTenuringDistribution
> - XX:+UseCMSInitiatingOccupancyOnly
> - XX:+UseConcMarkSweepGC
> - XX:+UseGCLogFileRotation
> - XX:-UseSuperWord
> - XX:CMSFullGCsBeforeCompaction=1
> - XX:CMSInitiatingOccupancyFraction=70
> - XX:CMSMaxAbortablePrecleanTime=6000
> - XX:CMSTriggerPermRatio=80
> - XX:GCLogFileSize=20M
> - XX:MaxTenuringThreshold=8
> - XX:NewRatio=2
> - XX:NumberOfGCLogFiles=9
> - XX:OnOutOfMemoryError=/usr/local/solr-6.4.1/bin/oom_solr.sh 8983
> /usr/local/solr-6.4.1/example/techproducts/solr/../logs
> - XX:PretenureSizeThreshold=64m
> - XX:SurvivorRatio=15
> -
> XX:TargetSurvivorRatio=90-Xloggc:/usr/local/solr-6.4.1/example/techproducts/solr/../logs/solr_gc.log-Xms21g-Xmx21g-Xss256k-verbose:gc
> Bug :
> In this version, there must be issue regarding cpu utilization.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
