You could also check the default memory by starting solr with the -V parameter for verbose output. It will show your output like this.
If your are startinf solr with script present in bin directory using this command *./solr -c -V* Using Solr root directory: /data/solr/aman/solr_cloud/solr-5.0.0 > Using Java: java > java version "1.7.0_75" > OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-1~trusty1) > OpenJDK Server VM (build 24.75-b04, mixed mode) > Backing up /xyz/bbc/qwe/solr_cloud/solr-5.0.0/server/logs/solr.log > Backing up /xyz/bbc/qwe/solr_cloud/solr-5.0.0/server/logs/solr_gc.log > Starting Solr using the following settings: > JAVA = java > SOLR_SERVER_DIR = /xyz/bbc/qwe/solr_cloud/solr-5.0.0/server > SOLR_HOME = /xyz/bbc/qwe/solr_cloud/solr-5.0.0/server/solr > SOLR_HOST = > SOLR_PORT = 4567 > STOP_PORT = 3567 > * SOLR_JAVA_MEM = -Xms512m -Xmx512m* > GC_TUNE = -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:CMSFullGCsBeforeCompaction=1 -XX:CMSTriggerPermRatio=80 > GC_LOG_OPTS = -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails > -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime > -Xloggc:/data/solr/aman/solr_cloud/solr-5.0.0/server/logs/solr_gc.log > SOLR_TIMEZONE = UTC > CLOUD_MODE_OPTS = -DzkClientTimeout=15000 -DzkHost=192.168.6.217:2181, > 192.168.5.81:2181,192.168.5.236:2181 > With Regards Aman Tandon On Thu, Mar 12, 2015 at 1:19 PM, Karl Kildén <karl.kil...@gmail.com> wrote: > Actually the reason I did not use the solr script was that I didn't really > get how to make a window service out of it from nssm.exe. I tried doing a > .bat that called solr with start -p 8983 but seems it just loops my command > rather then run it. > > Thanks for the help / Karl > > On 11 March 2015 at 23:08, Erick Erickson <erickerick...@gmail.com> wrote: > > > Well, the new way will be the only way eventually, so either you learn > > the old way then switch or learn it now ;)... > > > > But if you insist you could start with a heap size of 4G like this: > > > > java -Xmx4G -Xms4G -jar start.jar > > > > Best, > > Erick > > > > > > On Wed, Mar 11, 2015 at 1:09 PM, Karl Kildén <karl.kil...@gmail.com> > > wrote: > > > Thanks! > > > > > > I am using the old way and I see no reason to switch really? > > > > > > cheers > > > > > > On 11 March 2015 at 20:18, Shawn Heisey <apa...@elyograg.org> wrote: > > > > > >> On 3/11/2015 12:25 PM, Karl Kildén wrote: > > >> > I am a solr beginner. Anyone knows how solr 5.0 determines the max > > heap > > >> > size? I can't find it anywhere. > > >> > > > >> > Also, where whould you activate jmx? Would like to be able to use > > >> visualvm > > >> > in the future I imagine. > > >> > > > >> > I have a custom nssm thing going that installs it as a window > service > > >> that > > >> > simply calls java -jar start.jar > > >> > > >> The default heap size is 512m. This is hardcoded in the bin/solr > > >> script. You can override that with the -m parameter. > > >> > > >> If you are not using the bin/solr script and are instead doing the old > > >> "java -jar start.jar" startup, the default heap size is determined by > > >> the version of Java you are running. > > >> > > >> Thanks, > > >> Shawn > > >> > > >> > > >
