Tuning Endeca workbench JVM settings

We can increase the heap size for workbench to make it faster and more efficient by following below steps

1) Go to $ENDECA_TOOLS_ROOT/server/bin
2) Edit workbench .sh using following command
     vi workbench.sh
3) Check for following lines of commands :

# Prepend WB_CATALINA_OPTS to standard Workbench CATALINA_OPTS
CATALINA_OPTS="${WB_CATALINA_OPTS} -Xms256m"
CATALINA_OPTS="${CATALINA_OPTS} -Xmx1024m"
CATALINA_OPTS="${CATALINA_OPTS} -XX:MaxPermSize=512m"
CATALINA_OPTS="${CATALINA_OPTS} -Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=true"
CATALINA_OPTS="${CATALINA_OPTS} -Dcom.endeca.manager.endecaroot=${ENDECA_TOOLS_CONF}"
export CATALINA_OPTS

Replace CATALINA_OPTS="${CATALINA_OPTS} -Xmx1024m" with CATALINA_OPTS="${CATALINA_OPTS} -Xmx2048m"

Find RSS resident set size for MDEX

Resident set size (RSS) for MDEX is the amount of physical memory currently allocated and used by the MDEX Engine process

Check for MDEX and platformservice processes :

ps -ef | grep MDEX

mayank      15632 48215  0 13:02 ?        00:00:40 /tmp/endeca/MDEX/11.0.0/bin/dgraph --threads 14  --cmem 12288 --spl --spl_sthresh 150 --dym --dym_hthresh 5 --dym_nsug 1 --stat-abins --lang en --port 15000 --pidfile tmp/endeca/apps/EndecaApp/dgraph.pid --log tmp/endeca/apps/EndecaApp/logs/dgraphs/DgraphA1/DgraphB1.reqlog --out tmp/endeca/apps/EndecaApp/logs/dgraphs/DgraphA1/DgraphB1.log --spellpath tmp/endeca/apps/EndecaApp/data/dgraphs/DgraphA1/dgraph_input --updatedir tmp/endeca/apps/EndecaApp/data/dgraphs/DgraphA1/dgraph_input/updates --updatelog tmp/endeca/apps/EndecaApp/logs/dgraphs/DgraphA1/DgraphB1.updatelog tmp/endeca/apps/EndecaApp/data/dgraphs/DgraphA1/dgraph_input/EndecaApp
mbatra 19505 17549  0 14:11 pts/0    00:00:00 grep MDEX


This gives us two process ids viz - 15632


Next run following command :

ps -eo pid,ucomm,rss | grep 15632

15632 dgraph          1245698

This tells Resident set size for dgraph is 1.24 GB

Now check what is total infra memory you have :

free -m

                  total         used       free     shared    buffers     cached
Mem:        64586       5659     61256          1        629       2864
-/+ buffers/cache:       4521     62456
Swap:         4582          0         4582

This tells there is total of 61.2 gigs of memory is free and 5.6 gigs is being used (out of which 1.24 is being used by the dgraph)

Now you can decide if you want to add another dgraph to same server or need another server.

Unable to connect on workbench publishing port localhost/127.0.0.1:8007. Please check your assembler.properties file matches your webstudio.properties file for this port setting.

 SEVERE [com.endeca.infront.publish.AuthoringContentClient] (http-/127.0.0.1:8080-4) Exception while requesting a node from the server.: java.io.IOException: Unable to connect on workbench publishing port localhost/127.0.0.1:8007. Please check your assembler.properties file matches your webstudio.properties file for this port setting.

Check the Tools and framework service is running :

Windows : Go to windows "services" . If tools and frameworks is not started , start it

Linux : Run following  : ps -ef | grep java . Check for java process for ToolsAndFramework. If it is not running , go to /11.0.0/server/bin -> Execute ./startup.sh