AEM Replication agents - stuck

Avatar

Avatar
Validate 1
Level 1
tommyc11112341
Level 1

Likes

0 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Applaud 5
View profile

Avatar
Validate 1
Level 1
tommyc11112341
Level 1

Likes

0 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Applaud 5
View profile
tommyc11112341
Level 1

29-06-2021

Hi All,

 

 on high volume of activation tree replication agents stuck or going in block with high consumptions of machine resources. This lead to a restart of the AEM instances. To avoid this could be useful to enable "Batch Mode" on the replication agents?

 

image (1).png

 

Or as alternative upgrade the architecture with a replication-tier (merely a publish instances) between author and publish as follow:

 

- one replication agents on author (reduce replication event on author so author could not stuck)

- disable update assets on replication-tier (the assets are already elaborated from author)

- enable replication batch mode on the author and replication tier to stagger performance impact using the threshold level defined

 

Thanks a lot for any insight

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Affirm 50
Employee
markus_bulla_adobe
Employee

Likes

147 likes

Total Posts

126 posts

Correct reply

62 solutions
Top badges earned
Affirm 50
Boost 100
Applaud 25
Affirm 25
Boost 50
View profile

Avatar
Affirm 50
Employee
markus_bulla_adobe
Employee

Likes

147 likes

Total Posts

126 posts

Correct reply

62 solutions
Top badges earned
Affirm 50
Boost 100
Applaud 25
Affirm 25
Boost 50
View profile
markus_bulla_adobe
Employee

29-06-2021

Hi @tommyc11112341!

First of all, the outlined behavior sounds somewhat abnormal and the root cause should be analyzed and addressed.

That being said, the two approaches to deal with the situation that you mention are:

  1. Enabling batch mode for replication
  2. Moving to a replication-tier architecture

Option 1 is a quick and low-effort approach and therefore I would recommend to give it a try although I'm not convinced that it will lead to a final resolution of the issue (it will probably bring some improvement, though). It also comes with a couple of implication, e. g. pages not being replicated immediately after a content author hits the "publish" button. Depending on the replication traffic, it may take some time until the replication is actually executed. These are implications that need to be discussed with the business side and aligned with according requirements of your project. For more information on batch replication, please refer to the documentation of this feature.

Option 2 is a commonly used pattern for high replication volumes and will definitely address the issue. So if you have high replication traffic, this is a totally valid option to evaluate.

 

Hope that helps!

 

 

Answers (2)

Answers (2)

Avatar

Avatar
Affirm 25
Level 5
Bimmi_Soi
Level 5

Likes

72 likes

Total Posts

78 posts

Correct reply

26 solutions
Top badges earned
Affirm 25
Contributor
Applaud 5
Boost 50
Ignite 1
View profile

Avatar
Affirm 25
Level 5
Bimmi_Soi
Level 5

Likes

72 likes

Total Posts

78 posts

Correct reply

26 solutions
Top badges earned
Affirm 25
Contributor
Applaud 5
Boost 50
Ignite 1
View profile
Bimmi_Soi
Level 5

29-06-2021

@tommyc11112341 ,

 

enable replication batch mode on the author and replication tier to stagger performance impact using the threshold level defined as it would be the best approach in current scenerio.

 

Thanks

Avatar

Avatar
Boost 100
Level 6
Dipti_Chauhan
Level 6

Likes

114 likes

Total Posts

135 posts

Correct reply

40 solutions
Top badges earned
Boost 100
Give Back 10
Affirm 25
Boost 50
Boost 25
View profile

Avatar
Boost 100
Level 6
Dipti_Chauhan
Level 6

Likes

114 likes

Total Posts

135 posts

Correct reply

40 solutions
Top badges earned
Boost 100
Give Back 10
Affirm 25
Boost 50
Boost 25
View profile
Dipti_Chauhan
Level 6

29-06-2021

Hi @tommyc11112341 

   We use batch mode on all our lower environments. If there is no business need for immediate content activation than this is useful feature and it does improve replication performance.

 

Thanks

Dipti