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
            toddstoffel Todd Stoffel (Inactive) created issue -
            toddstoffel Todd Stoffel (Inactive) made changes -
            Field Original Value New Value
            Rank Ranked higher
            toddstoffel Todd Stoffel (Inactive) made changes -
            Assignee Alan Mologorsky [ JIRAUSER49150 ]
            toddstoffel Todd Stoffel (Inactive) made changes -
            Affects Version/s cmapi-6.4.1 [ 26900 ]
            toddstoffel Todd Stoffel (Inactive) made changes -
            Fix Version/s cmapi-6.4.2 [ 28333 ]
            toddstoffel Todd Stoffel (Inactive) made changes -
            Sprint 2021-17 [ 614 ]
            toddstoffel Todd Stoffel (Inactive) made changes -
            Rank Ranked lower
            toddstoffel Todd Stoffel (Inactive) made changes -
            Rank Ranked higher
            toddstoffel Todd Stoffel (Inactive) made changes -
            Rank Ranked higher
            toddstoffel Todd Stoffel (Inactive) made changes -
            Summary MCOL-4939 Causes Regression With Docker MCOL-4939 Causes Regression With Docker Clusters
            toddstoffel Todd Stoffel (Inactive) made changes -
            Description Whatever changes were implemented in MCOL-4939 have 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.

            I don't think this check was needed in the first place since we do not recommend customers to use local storage for metadata under any circumstance. I would like these changes backed out and the error message noted MCOL-5157 removed.             		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.

            I don't think this check was needed in the first place since we do not recommend customers to use local storage for metadata under any circumstance. I would like these changes backed out and the error message noted MCOL-5157 removed.
            toddstoffel Todd Stoffel (Inactive) made changes -
            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.

            I don't think this check was needed in the first place since we do not recommend customers to use local storage for metadata under any circumstance. I would like these changes backed out and the error message noted MCOL-5157 removed.             		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.

            CMAPI-6.4.1 refuses to continue unless auto_failover is set to false and even then it puts the cluster into an unusable state. It will not even complete table creation.

            I don't think this check was needed in the first place since we do not recommend customers to use local storage for metadata under any circumstance. I would like these changes backed out and the error message noted MCOL-5157 removed.
            toddstoffel Todd Stoffel (Inactive) made changes -
            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.

            CMAPI-6.4.1 refuses to continue unless auto_failover is set to false and even then it puts the cluster into an unusable state. It will not even complete table creation.

            I don't think this check was needed in the first place since we do not recommend customers to use local storage for metadata under any circumstance. I would like these changes backed out and the error message noted MCOL-5157 removed.             		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.

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

            I don't think this check was needed in the first place since we do not recommend customers to use local storage for metadata under any circumstance. I would like these changes backed out and the error message noted MCOL-5157 removed.
            toddstoffel Todd Stoffel (Inactive) made changes -
            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.

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

            I don't think this check was needed in the first place since we do not recommend customers to use local storage for metadata under any circumstance. I would like these changes backed out and the error message noted MCOL-5157 removed.             		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.

            CMAPI-6.4.1 refuses to continue unless auto_failover is set to false and 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, we do not sell the product this way and this has backfired on us.

            I would like these changes backed out and the error message noted MCOL-5157 removed.
            toddstoffel Todd Stoffel (Inactive) made changes -
            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.

            CMAPI-6.4.1 refuses to continue unless auto_failover is set to false and 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, we do not sell the product this way and this has backfired on us.

            I would like these changes backed out and the error message noted MCOL-5157 removed.             		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.

            CMAPI-6.4.1 refuses to continue unless auto_failover is set to false and 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 MCOL-5157 removed.
            toddstoffel Todd Stoffel (Inactive) made changes -
            Comment [ A comment with security level 'Developers' was removed. ]
            toddstoffel Todd Stoffel (Inactive) made changes -
            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.

            CMAPI-6.4.1 refuses to continue unless auto_failover is set to false and 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 MCOL-5157 removed.             		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

            CMAPI-6.4.1 refuses to continue unless auto_failover is set to false and 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 MCOL-5157 removed.
            toddstoffel Todd Stoffel (Inactive) made changes -
            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

            CMAPI-6.4.1 refuses to continue unless auto_failover is set to false and 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 MCOL-5157 removed.             		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 MCOL-5157 removed.
            toddstoffel Todd Stoffel (Inactive) made changes -
            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 MCOL-5157 removed.             		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.
            toddstoffel Todd Stoffel (Inactive) made changes -
            toddstoffel Todd Stoffel (Inactive) made changes -
            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.             		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
            toddstoffel Todd Stoffel (Inactive) made changes -
            toddstoffel Todd Stoffel (Inactive) made changes -
            toddstoffel Todd Stoffel (Inactive) made changes -
            toddstoffel Todd Stoffel (Inactive) made changes -
            toddstoffel Todd Stoffel (Inactive) made changes -
            Component/s cmapi [ 16117 ]
            Resolution Not a Bug [ 6 ]
            Status Open [ 1 ] Closed [ 6 ]
            toddstoffel Todd Stoffel (Inactive) made changes -
            Fix Version/s N/A [ 24311 ]
            Fix Version/s cmapi-6.4.2 [ 28333 ]
            toddstoffel Todd Stoffel (Inactive) made changes -
            Rank Ranked lower

            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.