[MGNLSYNC-17] Update synchronization module to do incremental updates/syncs to the webpub box instead of a complete synchronization of everything Created: 10/Jun/13  Updated: 02/Dec/22  Resolved: 02/Dec/22

Status: Closed
Project: Magnolia Synchronization Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Joey Reynolds Assignee: Unassigned
Resolution: Won't Fix Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Maintenance of Synchronization module
Team: Nucleus

 Description   

In our environment, we are working towards a complete automated environment where multiple servers can be brought in service or taken out based upon traffic load. We have a clustered environment of up to 6 servers currently taking traffic.

Currently when the application server is restarted on the webpub box, a complete synchronization is started even though the jcr is up to date. This complete synchronization takes over 17 mins to complete. Additionally, the synchronization sometimes locks the sync to other webpub servers in the cluster which can affect web-serving ability.

Overall, this impacts our ability to serve end-users well. We have the potential to be serving old data to the customers as well as not having enough servers completely ready to serve due to extensive time it takes to complete the sync.


Generated at Mon Feb 12 07:39:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.