[MCOL-2103]  columnstore_info.total_usage() returns irrelevant value Created: 2019-01-24  Updated: 2019-03-08  Resolved: 2019-01-25

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr
Affects Version/s: 1.1.7
Fix Version/s: 1.1.7

Type: Bug Priority: Major
Reporter: Zdravelina Sokolovska (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

mcs installation on 1UM-1PM, CentOS7.5


Issue Links:
Relates
relates to MCOL-1679 Wrong calculated total_disk_usage by... Closed

 Description   

columnstore_info.total_usage() returns irrelevant value

after loading 1TB data, columnstore_info.total_usage() returns
TOTAL_DISK_USAGE of 34.01 GB
while Disk usage on PM1 DBRoot 1 is 361G .

on mcs installation from scratch on 2 mcs modules(1um-1pm), load 1 TB data
get columnstore_info.total_usage()

From PM1, the disk usage on DBRoot 1 :
361G    /usr/local/mariadb/columnstore/data1

MariaDB [(none)]> call columnstore_info.total_usage();
+-----------------+------------------+
| TOTAL_DATA_SIZE | TOTAL_DISK_USAGE |
+-----------------+------------------+
| 576.95 GB       | 34.01 GB         |
+-----------------+------------------+
1 row in set (4.81 sec)
 
Query OK, 0 rows affected (4.81 sec)

# mcsadmin getStorageConfig
getstorageconfig   Thu Jan 24 11:12:21 2019
 
System Storage Configuration
 
Performance Module (DBRoot) Storage Type = internal
System Assigned DBRoot Count = 1
DBRoot IDs assigned to 'pm1' = 1

# mcsadmin getSystemDisk
getsystemdisk   Thu Jan 24 11:13:15 2019
 
System Disk Usage per Module
 
Module 'um1' Disk Usage (in 1K blocks)
 
Mount Point                    Total Blocks  Used Blocks   Usage %
-----------------------------  ------------  ------------  -------
/                              51368960      43481300         85
 
Module 'pm1' Disk Usage (in 1K blocks)
 
Mount Point                    Total Blocks  Used Blocks   Usage %
-----------------------------  ------------  ------------  -------
/                              1072681984    398840712        38
 
[root@pm1 ~]#
 



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2019-01-24 ]

This is very likely to be due to MCOL-2052. Can you please retry with a recent build that has that fix?

Comment by Zdravelina Sokolovska (Inactive) [ 2019-01-25 ]

 
Name        : mariadb-columnstore-platform
Version     : 1.1.7
Release     : 1
Architecture: x86_64
Install Date: Thu 24 Jan 2019 07:59:16 PM EET
Group       : Applications/Databases
Size        : 113742950
License     : Copyright (c) 2016 MariaDB Corporation Ab., all rights reserved; redistributable under the terms of the GPL, see the file COPYING for details.
Signature   : (none)
Source RPM  : mariadb-columnstore-platform-1.1.7-1.src.rpm
Build Date  : Thu 17 Jan 2019 06:16:39 AM EET
Build Host  : ip-10-0-0-129.ec2.internal
Relocations : (not relocatable)
Vendor      : MariaDB Corporation Ab
URL         : http://mariadb.org
Summary     : MariaDB-Columnstore software
Description :
MariaDB Columnstore: a very fast and robust SQL database server
 
It is GPL v2 licensed, which means you can use the it free of charge under the
conditions of the GNU General Public License Version 2 (http://www.gnu.org/licenses/).
 
MariaDB documentation can be found at https://mariadb.com/kb
MariaDB bug reports should be submitted through https://jira.mariadb.org

MariaDB [(none)]> call columnstore_info.total_usage();
+-----------------+------------------+
| TOTAL_DATA_SIZE | TOTAL_DISK_USAGE |
+-----------------+------------------+
| 576.95 GB       | 360.13 GB        |
+-----------------+------------------+

Comment by Costin Stefan [ 2019-03-08 ]

This bug is affecting also columnstore version 1.2. I've reproduced it on version 1.2.2.
Are you going to merge the fix in 1.2 branch?

Comment by Andrew Hutchings (Inactive) [ 2019-03-08 ]

costins The fix for this is in the 1.2 tree already and will be released as part of 1.2.3.

Generated at Thu Feb 08 02:33:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.