Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Not a Bug
-
cmapi-6.4.1
-
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.
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
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Assignee | Alan Mologorsky [ JIRAUSER49150 ] |
| Affects Version/s | cmapi-6.4.1 [ 26900 ] |
| Fix Version/s | cmapi-6.4.2 [ 28333 ] |
| Sprint | 2021-17 [ 614 ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 |
| Comment | [ A comment with security level 'Developers' was removed. ] |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 |
| Description |
Whatever changes were implemented in 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 |
Whatever changes were implemented in 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 All of this is made moot by MCOL-4218 anyway |
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
| Component/s | cmapi [ 16117 ] | |
| Resolution | Not a Bug [ 6 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Fix Version/s | N/A [ 24311 ] | |
| Fix Version/s | cmapi-6.4.2 [ 28333 ] |
| Rank | Ranked lower |
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 ?
yep.. lets wait for dleeyh and toddstoffel to provide an exact repro
then dev will look at it