[MCOL-3685] CREATE TABLE on UM successful without having PMs configured Created: 2019-12-20  Updated: 2021-01-15

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: 1.4.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Ralf Gebhardt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

CentOS 7


Attachments: File columnstoreSupportReport.columnstore-1.tar.gz    

 Description   

A CREATE TABLE is successful on a UM although the PM is not yet configured.

1. Install Server and ColumnStore engine via RPM (do not run columnStore-post-install and postConfigure
2. Start Server

 
MariaDB [test]> create table t1 (id int) engine=columnstore;
ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [test]> create table t1 (id int) engine=columnstore;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    8
Current database: test
ERROR 1050 (42S01): Table 't1' already exists
MariaDB [test]> show tables;
+----------------+
| Tables_in_test |
+----------------+
| t1             |
+----------------+
1 row in set (0.000 sec)
MariaDB [test]> show create table t1;
+-------+---------------------------------------------------------------------------------------------+
| Table | Create Table                                                                                |
+-------+---------------------------------------------------------------------------------------------+
| t1    | CREATE TABLE `t1` (
  `id` int(11) DEFAULT NULL
) ENGINE=Columnstore DEFAULT CHARSET=latin1 |
+-------+---------------------------------------------------------------------------------------------+
1 row in set (0.000 sec)
MariaDB [test]> insert into t1 values (1);
ERROR 1815 (HY000): Internal error: Lost connection to DMLProc after getting a new client [2:InetStreamSocket::connect: connect() error: Permission denied to: InetStreamSocket: sd: 46 inet: 0.0.0.0 port: 8614 then InetStreamSock

Creating a table should not be possible if the data node is not configured/accessible



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2019-12-22 ]

This shouldn't happen but there is something else underlying going on here. Please create a support report so we can figure it out (please note the tool is installed in /usr/bin in 1.4):

https://mariadb.com/kb/en/library/system-troubleshooting-mariadb-columnstore/#mariadb-columnstore-support-report-tool

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