Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega Index directory size growing drastically



An environment has been running with a 50 GB drive allocated for storing the Pega indexes.

For the past several days the index size has grown drastically and the current size is 126GB. Two days ago, they were around 80 GB in size.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

A defect or configuration issue in the operating environment:

70000 work objects were imported into the environment which have an issue where binary image data is stored in the blob.


Here’s the explanation for the reported behavior:

When creating new work objects that are taking up large amounts of space, one can exclude that class from search so they are not indexed.

This can be done from the Advanced tab on the Class rule (checkbox 'Exclude this class from search').

This will prevent any newly created work objects or updates from being indexed, but obviously these work objects won't be searchable.

If the data model is corrected so that binaries are stored in an attachment table instead of in the blob, user can then re-enable search. If corrected with existing work objects, one can reindex that class and this should reduce the size of the index files.

Published April 2, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us