[MDEV-27640] mariadb client hangs when starting to access a database with 300 600-column tables Created: 2022-01-27  Updated: 2022-01-27  Resolved: 2022-01-27

Status: Closed
Project: MariaDB Server
Component/s: Scripts & Clients
Affects Version/s: 10.6.5
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Daniel Lee (Inactive) Assignee: Sergei Golubchik
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

Centos 8 VM, 32GB memory


Attachments: File createTablesInnodb.sh     File wideTableInnodb-1.sql    

 Description   

Build tested: ColumnStore 6.2.2-1
Server version: 10.6.5-2-MariaDB MariaDB Server

After creating 300 600-column InnoDB tables using the attached scripts, the following command would hang. Is there a server setting the would help with this situation?

[centos8:root~]# mariadb mytest
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

It also hang with the following

[centos8:root~]# mariadb
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 1811
Server version: 10.6.5-2-MariaDB MariaDB Server
 
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
MariaDB [(none)]> use mytest
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Accessing the same database this way works fine

mariadb mytest -e 'show tables;'

It does not hang when accessing other databases. While hanging, the mariadb process is utilizing almost 100% CPU.

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                                            
  11847 root      20   0   57156  23804   7260 R  99.0   0.1   0:12.63 mariadb                                                                  



 Comments   
Comment by Sergei Golubchik [ 2022-01-27 ]

No, there is a client setting that would help with this situation. You've pasted it twice yourself:

Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Generated at Thu Feb 08 09:54:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.