Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Understanding replication agents

Avatar

Avatar
Validate 1
Level 2
shehjadk2932098
Level 2

Likes

2 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 2
shehjadk2932098
Level 2

Likes

2 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
shehjadk2932098
Level 2

07-05-2019

Hi All, I have question on how replication agents works. In AEM I have a workflow which have a out of the box Activate asset/page step after that I have to send a pubsub message to some caching services to clear cache and pull the latest content. In total I have 4 publisher and thus 4 replication agents are used to publish to 4 publish. So my question is it is possible that in my workflow step my workflow moves to next step (send message to cache service) before content have actually been replicated to all 4 publish server. In that case it is possible for those caching server to pull out dated content and thus have inconsistent content on different servers. Or the replication steps makes sure that content is successfully replicated to all 4 servers then only the step moves to next step in workflow? Any inputs on this would be very useful. I am using AEM 6.4.2 Thanks, Shehjad

Replies

Avatar

Avatar
Give back 300
MVP
Gaurav-Behl
MVP

Likes

243 likes

Total Posts

1,145 posts

Correct Reply

281 solutions
Top badges earned
Give back 300
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Give back 300
MVP
Gaurav-Behl
MVP

Likes

243 likes

Total Posts

1,145 posts

Correct Reply

281 solutions
Top badges earned
Give back 300
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile
Gaurav-Behl
MVP

07-05-2019

Per my knowledge, it is possible that your workflow step could advance to next step and cache is not yet published. It depends on your setup and network latency and size of content package to be replicated.

You could add a custom workflow step to listen/process the response code of replication action and then move to next step.