Source Environment Clustering And Publishing Related Questions (Doc ID 2777033.1)

Last updated on SEPTEMBER 15, 2021

Applies to:

Goal

Currently we have our source contribution environment configured to have just one node. It then publishes to multi other clustered environments.
We find that when publishing to a new destination environment (all content) we have to do this out of normal working hours.

This is because all assets that being published will be placed into the publishing queue and therefore stop editors from doing their work on a particular asset or assets until they are all published.

We are looking at re-creating our source contribution environment to be clustered (maybe 3 nodes) primarily for HA reasons.

However I believe that we will still have the same issue when it comes to publishing is that right?
The assets will be locked across all nodes? The benefit we will have is that we can publish from any of the nodes.

Further questions :-
- Is there anyway to enable editors to continue whilst a publish is happening and not get blocked in potentially multi-node environment?
- Our initial publish currently can take around 7 to 8 hours.
- Are there any recommendations on how best for to setup the source contribution for HA etc?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.