Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5069

Don't overwrite CS configuration during upgrade

    XMLWordPrintable

    Details

      Description

      Ask:
      Do not change current configuration during CS upgrade

      Details:
      When columnstore is upgraded the old settings and configuration files are overwritten/moved and this causes issues for customers not expecting it. Their cluster doesn't come back up and after troubleshooting they realize they also lost their settings.

      I would hope that we could just check for the files during install and reuse them if they already exist. If not new ones are created.

      Another way would be just to have the new ones install as .template or .sample files so they won't overwrite existing files.

      Versions:
      CS: 6.1.1 to 6.3.1
      cmapi: 1.6 to 1.6.3

      Update: It was also mentioned by the team that we need to keep the systemd timeout tweaks in the installation package instead.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            luke.smith Luke
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.