Two publisher of same project have different repository size

[bhagchand]

Hi All,

Hope you are doing.

In our production environment we have two publisher with same code, content and configuration. Yesterday we have checked and noticed that their repository have different size. 

We also enabled sticky connection over dispatcher.

Any suggestions please.

[A_H_M_Imrul]

@bhagchand

What do you mean by repository size?

If you are referring to the content repository, please check the package manager, there might packages manually build in one publisher which are not available on the other one.

See if this make sense, you can share more detail for better help..

[bhagchand]

Packages and code all are same on both publishers. 

What do you mean by repository size?-  crx-quickstart/repository here is  size difference .

This is happen due to sticky connection enabled on dispatcher?

[A_H_M_Imrul]

"This is happen due to sticky connection enabled on dispatcher?" I don't think so, unless you are generating content from publishers (storing it on publisher).

Can you check folders(like datastore, index etc.) sizes under crx-quickstart/repository?

[bhagchand]

Let me check 

[aanchal-sikka]

Hello @bhagchand 

• Can you please check if the replication settings "Serialization Type" are same for the replication agent to both the publishers?

• Please check if the maintenace tasks like "Garbage collection" and "Revision cleanup" is completing in both the instances

[bhagchand]

Thanks let me check,  @A_H_M_Imrul @aanchal-sikka  we have download the error logs for both publisher and one have size 70MB and another one have 50MB

[bhagchand]

Hi @aanchal-sikka ,  "Serialization Type" is default in both publisher, any other 

[aanchal-sikka]

@bhagchand 

Please check if the Maintenace tasks like "Garbage collection", "Revision cleanup" etc completing in both the instances.

[Jagadeesh_Prakash]

@bhagchand  There could be many factors for this issue. 

Content Differences, Data Migration, Backup and Restore, Cache and Revision Cleanup, Configuration Differences, Audit Logs and Logging, Binary Data, Custom Code and Workflows, Sticky connection

To resolve the differences in repository size and maintain consistency between the two AEM publishers, you should:

• Perform a thorough content audit to identify discrepancies in content between the two publishers.
• Ensure that data migration and synchronization processes are correctly configured and run at the same time on both publishers.
• Review and align configuration settings between the two publishers.
• Monitor and manage binary assets and content revisions to prevent unnecessary growth in the repository.

But wanted to understand what does it make any difference have 2 difference sizes for publishers ? Just trying to understand

[kautuk_sahni]

@bhagchand  Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

[Hemalatha]

Hi @bhagchand 

You can compare both the repositories using the ACS Commons JCR Compare feature,

https://adobe-consulting-services.github.io/acs-aem-commons/features/jcr-compare/index.html

You can also try offline compaction of the publisher which is having larger size than the other if you are not finding any content difference form the above.  Hope this helps.

Regards,

Hemalatha