Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-20706

Need a documented process for rolling back a deployment

    Details

    • Type: Improvement
    • Status: Closed
    • Resolution: Won't Do
    • Affects Version/s: 5.2.3
    • Fix Version/s: None
    • Component/s: Repository, Upgrades
    • Labels:
      None
    • Bug Priority:
      Category 4
    • ACT Numbers:

      00991052

    • Premier Customer:
      Yes

      Description

      A premier customer has deployed alfresco in AWS using containers. As part of their release they deploy new wars by changing the docker image version, if the customer needs to rollback a release they rollback the DB, indices and contentstore to the time before the release.

      They need to do all this because if they deploy new amps/modules these new versions are persisted in the DB. This brings up a problem when rolling back the DB (Aurora mysql), the rollback process takes over 2 hours to complete, the customer would like to know if there's a list of tables they need to rollback after a new war deployment to minimize the time it takes to rollback the entire alfresco db?

      Can we have documentation on best practices for reverting a new war deployment with minimal downtime?

       

       

        Attachments

          Structure

            Activity

              People

              • Assignee:
                closedissues Closed Issues
                Reporter:
                jportillo Jose Portillo
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel