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

MCOL-4939 Causes Regression With Docker Clusters

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Not a Bug
    • cmapi-6.4.1
    • N/A
    • cmapi
    • None
    • 2021-17

    Description

      Whatever changes were implemented in MCOL-4939 included some logic to determine whether or not shared storage is being used. This check is inadequate as it fails to recognize shared volumes within a Docker environment and this will break our publicly facing Docker projects as well as SkySQL.

      https://github.com/mariadb-corporation/mariadb-enterprise-columnstore-docker/blob/master/docker-compose.yml#L30-L34

      In this case, CMAPI-6.4.1 refuses to continue unless auto_failover is set to false but even then it puts the cluster into an unusable state. Columnstore will not even complete a simple table creation.

      I don't think this local storage check was needed in the first place since we do not recommend customers to use local storage for metadata under any circumstance and we do not sell the product in that way.

      I would like these changes backed out and the error message noted in MCOL-5157 removed.

      All of this is made moot by MCOL-4218 anyway

      Attachments

        Issue Links

          is caused by

          New Feature - A new feature of the product, which has yet to be developed. MCOL-4939 Add a method to disable failover facility in CMAPI.

          • Major - Major loss of function.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MCOL-4218 Remove NFS/EFS/ Filestore prereq for S3 storage

          • Critical - Crashes, loss of data, severe memory leak.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MCOL-5157 Remove Unnecessary Message about Failover in CMAPI Log.

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            alexey.vorovich alexey vorovich (Inactive) added a comment -

            yep.. lets wait for dleeyh and toddstoffel to provide an exact repro
            then dev will look at it

            alexey.vorovich alexey vorovich (Inactive) added a comment - yep.. lets wait for dleeyh and toddstoffel to provide an exact repro then dev will look at it
            alexey.vorovich alexey vorovich (Inactive) added a comment -

            dleeyh alan.mologorsky do we have a reproduction here and how is it different from the stand docker compose we have been running all along

            alexey.vorovich alexey vorovich (Inactive) added a comment - dleeyh alan.mologorsky do we have a reproduction here and how is it different from the stand docker compose we have been running all along
            alexey.vorovich alexey vorovich (Inactive) added a comment -

            toddstoffel my initial reaction is that we need to protect ourselves from this .
            So when you built the 614 handoff the upstream server latest version moved .
            should we adjust process this moving forward ?

            alexey.vorovich alexey vorovich (Inactive) added a comment - toddstoffel my initial reaction is that we need to protect ourselves from this . So when you built the 614 handoff the upstream server latest version moved . should we adjust process this moving forward ?

            People

              alan.mologorsky Alan Mologorsky
              toddstoffel Todd Stoffel (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.