[MCOL-3568] calshowpartitions no reporting any partition Created: 2019-10-18 Updated: 2023-03-06 Resolved: 2023-03-06 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | N/A |
| Affects Version/s: | 1.1.6 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Customer report: calshowpartitions no reporting any partition We have right now an issue with our MariaDB Columnstore installation. System doesn't report any partition with any table (although almost all tables have millions of records). Response is always empty: For instance:
------------------------------------------------------------------------------
------------------------------------------------------------------------------ We use this information to check with partitions we can drop (the oldest ones) so we currently we are not dropping any partition for any table, Right now, our data filesystem is completely full and we can't add any data to our DB. As additional information, in case it is related, recently we had an issue derived from "umask" configuration. Administrators change this value and DB could not start because file "Columstore.xml" was owned by "root" with no read permission to other users (mysql in this case). Umask is correct right now as required. We think it must be related (perhaps another file with no permissions to "mysql" user), but we don't know. |
| Comments |
| Comment by David Hill (Inactive) [ 2019-10-23 ] |
|
from customer The "calShowPartitions" command still does not report any partition, so we are in the initial situation Using the information offered by the "editem" command we have been able to see which partitions we could eliminate (based on the historical data required by each table), and we have verified that the "calDropPartitions" command does work if we indicate a correct partition . With this we will erase daily partitions by hand waiting for you to find out why we do not visualize the partitions as would be expected. |
| Comment by David Hill (Inactive) [ 2020-05-04 ] |
|
Update from customer Incidence still occurs. We have not yet been able to update the database version (it does not depend on us but on our client). In any case we changed the automatic processes of purging partitions using the information of the command "editem" instead of "calShowPartitions", and with this we have the system properly maintained. |
| Comment by Jimmy Atauje Hidalgo [ 2020-10-08 ] |
|
Hi the same situation is happening to me on Columnstore 1.1.6-1 using "editem" is a nice workaround. maybe a cache issue? |
| Comment by Todd Stoffel (Inactive) [ 2023-03-06 ] |
|
This ticket was opened prior to convergence with the server. It may have been rendered obsolete. If this issue still exists in a modern version, please open a new request. |