Details

    • Type: Epic
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Epic Status:
      To Do

      Description

      Although the most common use case is to use the upgrade tool with a backup of the database, in some scenarios like in cloud or for micro upgrade processes, the upgrade run can run on start up or demand via gogo shell. If a cluster is enabled in those cases, we can have issues since the process can start in several servers at the same time.

      Team Goals and Business Objectives
      Make the execution of upgrade processes on cluster environments via startup (upgrade.database.auto.run=true) or via gogo shell safe.

      The upgrade tool is not affected by this change since it is a standalone tool

      Requirements
      1. If an upgrade process is executed when the server is up, ensure that only runs in one node. We can run upgrade processes only in the master node if that simplifies the solution, other options are feasible.
      2. Ensure the data modified by the upgrade process is up to date in other nodes too (verify the cache so the nodes are sync after the changes)

        Attachments

          Activity

            People

            Assignee:
            team-upgrades Product Team Upgrades
            Reporter:
            alberto.chaparro Alberto Chaparro
            Recent user:
            Alberto Chaparro
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:

                Packages

                Version Package