[MGNLSYNC-41] Add support for parallelization of synchronization Created: 06/Jan/20  Updated: 28/Jun/22

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

Type: Improvement Priority: Neutral
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLSYNC-40 Add support for invoking synchronizat... Closed
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)
Epic Link: Maintenance of Synchronization module
Team: Nucleus

 Description   

Currently synchronization assumes that all public instances are out of sync and tries to synchronize all existing ones. This, together with time necessary to run synchronization prevents possibility of synchronizing publics one-by-one as they come up.

Scenario:
The scenario is that you want to trigger sync over rest from headless env. it’s not human doing the invocation but a bot.

Proposed solution:

  • separate synchronization configuration from publishing configuration
  • allow each job to have configuration provided either by parameters or be able to use unique per-job configuration by other means (e.g. having multiple configurations for subscribers under module configuration and referencing them by configuration name from the job)
  • prevent execution of multiple synchronizations against same public instance, while allowing multiple synchronization jobs to run at the same time.

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