O&M Question about pega.tmpdir=/$base_dir/temp/pegatemp
All,
As my systems age and become more stable I find that my pega.tmpdir=/$base_dir/temp/pegatemp Directory is filling up. What is the recommended method for recapturing this space not requiring an application stop/start?
Currently we perform the following when we want a clean start
Pega 6.3 sp1 on Linux
shopt -s extglob
rm -rf /$base_dir/temp/pegatemp/!(PegaRULESIndex)
rm -rf /$base_dir/temp/javatemp/*
rm -rf /$base_dir/jboss/jboss-eap-5.1/jboss-as/server/pega/{tmp,data}
Thank you,
Ray
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accenture Federal
US
I am removing everything except the Index.
This is the size of the index
| 11G | ./PegaRULESIndex/DataIndex |
| 408M | ./PegaRULESIndex/RuleIndex |
| 100M | ./PegaRULESIndex/WorkIndex |
| 11G | ./PegaRULESIndex |
Filesystem Size
50G 12G 35G 26% /$base_dir
It seems that most of the size is taken up by the DataIndex which suggests that the work attachments are contributing to this size. If the users don't need searching in the attachments, disable attachment indexing in the search landing page.
Updated: 23 Jul 2015 1:37 EDT
Pegasystems
IN
Hi Vipin,
Small correction. Attachments are stored in the Work index and not in the Data index. This allows us to track attachments better and also return the work object to which this attachment is associated with.
Note that for Data index we only store the instances of those classes which have a ruleform associated with them.
I suggest we use Luke (luke - Luke - Lucene Index Toolbox - Google Project Hosting) to look into the index and see which class instances are causing the index size to be so big.
-Rajiv