If you are using 7.1.8, it should be an Elastic Search index (which uses Lucene underneath).
The size of the index grows the number of cases, rules or data instances grows in your database.
Could you please let us know what the current index size is?
Also, the time taken to index is dependent on the number of cases, rules and data and the size of each instance. You can roughly approximate the size of an instance by doing a length on the BLOB column.
Note that Elastic Search indices (Lucene indices) grow and shrink as indexing updates the index with entries in it. This results in the index actually consuming up to 3 times the size of the index if it was freshly built.
We are in the process of combining a PEGA 6.1 & PEGA 6.2 environment into an updated PEGA 7.1.8.
Does the mean that all applications will be hosted on the same Pega cluster (a Pega cluster is all application server nodes pointing to the same PegaRULES DB schema)?
If that is not the case, then each cluster should have its own set of index nodes and that should help.
So yes, I see concerns with a growing index file, but only if, for whatever reason, we need to rebuild if from scratch.
I can see the concern here. A general understanding of your growth rate would help understand this better. Also, if you have any archive & purge policy, then that would be useful to know.
Posted: 5 years ago
Posted: 5 Dec 2016 20:19 EST
DILIP MONDAL (DilipKMondal)