Recommend backporting this to 1.0 if we do another release.

Need to add a warning in the documentation that this shouldn't be run by more than one client at the same time (the new version of table_usage will have problems if you try).

Anyone who is hit with this problem can fix it on their own installation by manually piping this version of columnstore_info.sql into their mariadb client as root.

Second pull request adds safety locks as discussed with David Hall.

Build tested:
[root@localhost columnstore]# cd mariadb-columnstore-server/
[root@localhost mariadb-columnstore-server]# git show
commit 3da188e5c8a2630019ea810fb8c1bd3ece5e058b
Merge: 5d9686c 53c1df7
Author: Andrew Hutchings <andrew@linuxjedi.co.uk>
Date: Fri Feb 10 15:07:31 2017 +0000

Merge pull request #31 from jbfavre/fix_deb_package_dependency

MCOL-562 Fix Debian package dependencies

[root@localhost mariadb-columnstore-server]# cd mariadb-columnstore-engine/
[root@localhost mariadb-columnstore-engine]# git show
commit 16cef50caedd9ec7585b04c096996a9441bdf2d5
Author: David Hill <david.hill@mariadb.com>
Date: Wed Mar 1 10:39:11 2017 -0600

change the check for prompt back to the previous code

Tested with concurrent sessions. While session 1 is running, session 2 return the following, which is the expected behavior.

MariaDB [tpch10c]> call columnstore_info.table_usage(NULL,NULL);
ERROR 1644 (45000): Error acuqiring table_usage lock

"acquiring" spelling is incorrect.
MariaDB [tpch10c]> call columnstore_info.table_usage(NULL,NULL);
-----------------------------------------------------------------

-----------------------------------------------------------------

-----------------------------------------------------------------
9 rows in set (5.37 sec)

Query OK, 0 rows affected (5.37 sec)

Results are in bytes only. It should display in mb, gb.

Per my last comment

Fix for units and spelling error that Daniel spotted

Build verified: Github source

[root@localhost mariadb-columnstore-server]# git show
commit 3da188e5c8a2630019ea810fb8c1bd3ece5e058b
Merge: 5d9686c 53c1df7
Author: Andrew Hutchings <andrew@linuxjedi.co.uk>
Date: Fri Feb 10 15:07:31 2017 +0000

Merge pull request #31 from jbfavre/fix_deb_package_dependency

MCOL-562 Fix Debian package dependencies

[root@localhost mariadb-columnstore-engine]# git show
commit f19710126a9a523eccf2d65b022086cc44cde53e
Merge: 86ddc8a c6000d3
Author: dhall-InfiniDB <david.hall@mariadb.com>
Date: Thu Mar 2 14:41:51 2017 -0600

Merge pull request #129 from mariadb-corporation/MCOL-533-format

MCOL-533 fix units for table_usage

Verified the latest fixes.

re-opening to backport to 1.0.8

New pull request for backport to 1.0

Tested in 1.0.8-1 on a 1um2pm stack

MariaDB [(none)]> use tpch10c
Database changed
MariaDB [tpch10c]> call columnstore_info.table_usage(NULL,NULL);
ERROR 1105 (HY000): Unknown error 0% of stage done
MariaDB [tpch10c]> call columnstore_info.table_usage(NULL,NULL);
ERROR 1644 (45000): Error acquiring table_usage lock

There are crit.log and err.log files in all three nodes. Therefore, no errors have been logged.

This problem is the one in MCOL-605. I suggest retesting once that is merged.

Build verified: 1.0.8-1

mcsadmin> getsoftware
getsoftwareinfo Wed Mar 22 22:47:15 2017

Name : mariadb-columnstore-platform
Version : 1.0.8
Release : 1
Architecture: x86_64
Install Date: Wed 22 Mar 2017 09:37:39 PM UTC
Group : Applications/Databases
Size : 10012539
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.0.8-1.src.rpm
Build Date : Wed 22 Mar 2017 08:41:24 PM UTC
Build Host : ip-172-30-0-125.us-west-2.compute.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

MariaDB [(none)]> call columnstore_info.table_usage(NULL,NULL);
-----------------------------------------------------------------

-----------------------------------------------------------------

-----------------------------------------------------------------
9 rows in set (0.92 sec)

Query OK, 0 rows affected (0.92 sec)

MariaDB [(none)]> call columnstore_info.table_usage(NULL,NULL);
ERROR 1644 (45000): Error acquiring table_usage lock

On a 1um2pm stack, it is hard to see the locking mechanism working, since the query does not take long to execute. Testing with two session right after the ColumnStore has been restarted has a higher chance of see the lock.

Build verified: 1.1.0 GitHub source
[root@localhost mariadb-columnstore-server]# git show
commit 24f5065dba978ef4ec6ea8cb4bfd9728321941bd
Author: david hill <david.hill@mariadb.com>
Date: Mon Mar 20 09:57:25 2017 -0500
[root@localhost mariadb-columnstore-engine]# git show
commit ff36e8e774fd961625d42b45070f56bead83a5bc
Merge: c1d38e0 6ab434e
Author: dhall-InfiniDB <david.hall@mariadb.com>
Date: Wed Mar 22 15:16:53 2017 -0500
Merge pull request #139 from mariadb-corporation/MCOL-605-hotfix
MCOL-605 Fix multi-node "Unkown error"

MariaDB [(none)]> call columnstore_info.table_usage(NULL,NULL);
-----------------------------------------------------------------

-----------------------------------------------------------------

-----------------------------------------------------------------
9 rows in set (0.59 sec)

MariaDB [(none)]> call columnstore_info.table_usage(NULL,NULL);
ERROR 1644 (45000): Error acquiring table_usage lock

Closed per my last comment.