TarMK standby node sync Bundles in AEM 6.4 | Community
Skip to main content
F
FrancescoMa2
February 28, 2024
Solved

TarMK standby node sync Bundles in AEM 6.4

  • February 28, 2024
  • 2 replies
  • 767 views

Hello everyone,

 

We need help to understand if TarMK synchronisation process is working correctly between the primary node Author and the standby node Author.

Our checks show that the process is current and up-to-date.

However, upon comparing the bundles of the primary node and the bundles of the standby node, there appears to be a mismatch (different versions and missing bundles).

We assumed that the mismatch of the bundles is only 'visual', as the contents/bundles of the primary node are correctly transferred and synchronised on the standby node according to tarmk-coldstandby.log.

However, in our opinion because of the "standby" state, the contents/bundles are not correctly updated from the web console "/system/console/bundles", as long as the node's state is not active.

Only once the state change from standby to primary has been made, the node in question should read and update the information it contains, and finally resulting up to date.

 

Our hypothesis is not covered by the documentation, can anyone confirm the described behavior is correct or do we have some kind of synchronisation bug?

 

N.B.: Starting the standby node as primary, to be able to check the actual situation, is possible for us but highly problematic (organisational issues).

 

Thank you for your precious support.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by EstebanBustamante

Hi, 


Here is a well-explained explanation of the behavior regarding the bundles: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/osgi-bundles-jar-s-not-getting-synced-in-aem-6-2-cold-standby/m-p/210371/highlight/true#M6374 Although it may not necessarily clear your doubt about the bundles' version if you set your TarMk log to debug and check for any issues in the sync process and find none, it is safe to assume that the sync is working as expected.  I guess the best option to confirm your hypothesis about the number of bundles is to give it a try, use the standby instance, and check if those numbers get updated

 

 

Hope this helps.

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
February 28, 2024

Hi, 


Here is a well-explained explanation of the behavior regarding the bundles: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/osgi-bundles-jar-s-not-getting-synced-in-aem-6-2-cold-standby/m-p/210371/highlight/true#M6374 Although it may not necessarily clear your doubt about the bundles' version if you set your TarMk log to debug and check for any issues in the sync process and find none, it is safe to assume that the sync is working as expected.  I guess the best option to confirm your hypothesis about the number of bundles is to give it a try, use the standby instance, and check if those numbers get updated

 

 

Hope this helps.

Esteban Bustamante
    F
    FrancescoMa2Author
    March 7, 2024

    Thank you for your answer,  it turns out that bundles are updated at the last time the node was started as primary. So all the bundles are syncing but you can't see them until you switch between the two authors' nodes.

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      March 7, 2024

      @francescoma2 Did you find the suggestion helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...