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

Merge 3 MCS packages into a single-one

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 1.5.1
    • None
    • None

    Description

      We need to merge all three packages into a single one.

      At this point there will be no need to explicitly run columnstore-post-install or postConfigure, and by default the package installation provides a user with a single-node installation.
      All services control migrates to systemd.
      There will be cgroups rules that must be applied on installation.
      We must remove extra files left after uninstallation.:

      /var/log/mariadb/columnstore
      /tmp/columnstore_tmp_files
      /usr/share/columnstore
      

      Attachments

        Issue Links

          Activity

            Sorry, I merged this Friday evening, forgot to update the ticket.

            pleblanc Patrick LeBlanc (Inactive) added a comment - Sorry, I merged this Friday evening, forgot to update the ticket.

            Build verified: 1.5.0-1 (drone 20200602)

            This build supports single-node installation only.

            Verified the following:

            1. There is only one package for columnstore engine, such as
            MariaDB-10.5.4-centos7-x86_64-columnstore-engine.rpm
            2. ColumnStore, as well as its processes, are now services
            mariadb-columnstore.service
            mcs-controllernode.service
            mcs-ddlproc.service
            mcs-dmlproc.service
            mcs-exemgr.service
            mcs-loadbrm.service
            mcs-primproc.service
            mcs-storagemanager.service
            mcs-workernode.service
            mcs-writeengineserver.service
            3. Uninstall the engine package also removed the following directories
            /var/log/mariadb/columnstore
            /tmp/columnstore_tmp_files
            /usr/share/columnstore

            [centos7:root~]# rpm -ivh MariaDB-10.5.4-centos7-x86_64-columnstore-engine.rpm
            Preparing... ################################# [100%]
            Updating / installing...
            1:MariaDB-columnstore-engine-10.5.4################################# [100%]

            Performing the Single Server Install.

            Running the MariaDB ColumnStore setup scripts

            post-mysqld-install Successfully Completed
            post-mysql-install Successfully Completed

            dleeyh Daniel Lee (Inactive) added a comment - Build verified: 1.5.0-1 (drone 20200602) This build supports single-node installation only. Verified the following: 1. There is only one package for columnstore engine, such as MariaDB-10.5.4-centos7-x86_64-columnstore-engine.rpm 2. ColumnStore, as well as its processes, are now services mariadb-columnstore.service mcs-controllernode.service mcs-ddlproc.service mcs-dmlproc.service mcs-exemgr.service mcs-loadbrm.service mcs-primproc.service mcs-storagemanager.service mcs-workernode.service mcs-writeengineserver.service 3. Uninstall the engine package also removed the following directories /var/log/mariadb/columnstore /tmp/columnstore_tmp_files /usr/share/columnstore [centos7:root~] # rpm -ivh MariaDB-10.5.4-centos7-x86_64-columnstore-engine.rpm Preparing... ################################# [100%] Updating / installing... 1:MariaDB-columnstore-engine-10.5.4################################# [100%] Performing the Single Server Install. Running the MariaDB ColumnStore setup scripts post-mysqld-install Successfully Completed post-mysql-install Successfully Completed

            People

              dleeyh Daniel Lee (Inactive)
              drrtuy Roman
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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