Repository size is increasing frequently

[skumari1]

Hi Team

We are facing repository growth in one of our publisher. We have checked the maintenance console and its showing the DSGC run successfully but we found "Workflow purge is failing" . Also the DSGC run fine but we are old repository datastore inside our S3 bucket which is shared among other instances. So, our requirement here is to clean the old ones to reduce the repo size of Publish instance but we don't have much information  how to do this in safe manner.

Attaching some screenshots:-

There are many data like this from 2021.

[Sachin_Arora_]

Please confirm if repository size (segment store) is increasing or the datastore size(Binary files storage) is increasing? For big setups generally both are mounted to different storage.

[skumari1]

Ok, will let you know after clearing this.

[skumari1]

Hi Sachin

Segment store is increasing.

[Sachin_Arora_ · Accepted solution]

Please check if any thread is running in loops and causing size increase of the segment store. You can take thread dumps and verify . You can manually run workflow purge as well from JMX to see if that helps. Generally there should not be much workflows running on publish instance.
You can also plan for online or offline revision clean up. Offline revision clean up gives good result in terms of size reduction.
There is one simple way as well to replace this publisher instance crx-quickstart with that of stable publisher as you have mentioned its happening only for one publisher. This way your all publishers would be in same state. Ideally issue should come in all publishers.

Links

https://github.com/AdobeDocs/experience-manager-65.en/blob/main/help/sites-administering/troubleshoo...

JMX Workflow Maintenance : /system/console/jmx/com.adobe.granite.workflow%3Atype%3DMaintenance

[Manu_Mathew_]

@skumari1 Probably could try revision cleanup:

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/deploying/revision-cleanup.h...

[ShaileshBassi]

@skumari1 Every update to the repository creates a new revison, due to which size of the repository increases. And to avoid this unavoidable increase in size revision clean up should be run i.e. online or offline as suggested by @Manu_Mathew_ as well.

Reference Doc - https://experienceleague.adobe.com/docs/experience-manager-65/deploying/deploying/revision-cleanup.h...

Hope this helps!

Thanks

[skumari1]

Thanks for the all support, will suggest my team the above solutions.