Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-1076

Retry Algorithm for Module-Sync based on LockReason.Details (from last failure)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Kohn Release
    • None
    • NCMP

      Notes

      1. Poll execute for 'ADVISED' c-handles every 30 seconds
      2. Poll for CM-handles State 'LOCKED' & Reason 'LOCKED_CANNOT_SYNC_MODULES'  CM handles execute every 5 minutes
      3. We need a minimum time before retry (re-set to 'ADVISED') use  and CmHandle.lastUpdateTime to check this
        e.g 60 second (Configurable)
      4. Do we want back-of mechanism ie. double this time each attempt
        LockReason.details for #attempts
        Resulting 1-2-4-8-16-32-64-128-etc. minutes...
      5. NO need to give up, up to customer will have to re-register

      A/C

      1. Agree new ENUM value with stakeholders
      2. Demo using local logs (possibly manipulate code or tets setup to force retry for-ever)

       

            dylanb95est dylanb95est
            ToineSiebelink Toine Siebelink
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: