[MCOL-3613] postConfigure parameter numBlocksPct and totalUmMemory not applied in singlenode Created: 2019-11-14  Updated: 2019-11-18  Resolved: 2019-11-18

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.4.1
Fix Version/s: 1.4.1

Type: Bug Priority: Blocker
Reporter: Jens Röwekamp (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: SkySQLMVP
Environment:

CentOS 7 - 6571cafb4f9fff55a9a4cc147c4e19eb37b347f7


Sprint: 2019-06

 Description   

The -totalUmMemory option crashes postConfigure and the -numBlocksPct option isn't applied in SingleNode / Standalone.
We need both parameters for SkySQL to set the amount of memory manually.

Both parameters work as expected for multi node deployments.

[root@um1 jens]# postConfigure -x -xr -numBlocksPct 1024M -totalUmMemory 256M
This is the MariaDB ColumnStore System Configuration and Installation tool.
It will Configure the MariaDB ColumnStore System and will perform a Package
Installation of all of the Servers within the System that is being configured.
IMPORTANT: This tool requires to run on the Performance Module #1
Prompting instructions:
        Press 'enter' to accept a value in (), if available or
        Enter one of the options within [], if available, or
        Enter a new value
===== Setup System Server Type Configuration =====
There are 2 options when configuring the System Server Type: single and multi
  'single'  - Single-Server install is used when there will only be 1 server configured
              on the system. It can also be used for production systems, if the plan is
              to stay single-server.
  'multi'   - Multi-Server install is used when you want to configure multiple servers now or
              in the future. With Multi-Server install, you can still configure just 1 server
              now and add on addition servers/modules in the future.
Select the type of System Server install [1=single, 2=multi] (2) > 1
Performing the Single Server Install.
Enter System Name (columnstore-1) >
===== Setup Storage Configuration =====
----- Setup Performance Module DBRoot Data Storage Mount Configuration -----
Columnstore supports the following storage options...
  1 - internal.  This uses the linux VFS to access files and does
      not manage the filesystem.
  2 - external *.  If you have other mountable filesystems you would
      like ColumnStore to use & manage, select this option.
  3 - GlusterFS *  Note: glusterd service must be running and enabled on
      all PMs.
  4 - S3-compatible cloud storage *.  Note: that should be configured
      before running postConfigure (see storagemanager.cnf)
  * - This option enables data replication and server failover in a
      multi-node configuration.
These options are available on this system: [1, 2, 4]
Select the type of data storage (1) >
Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm1' (1) >
===== Performing Configuration Setup and MariaDB ColumnStore Startup =====
[root@um1 jens]# echo $?
0



 Comments   
Comment by Ben Thompson (Inactive) [ 2019-11-14 ]

Reviewed / Merged

Comment by Daniel Lee (Inactive) [ 2019-11-18 ]

Build verfied: 1.4.1-1 github source

Server
commit 77a245fe5658b8d6d937620586ecd802b3432a78
Author: Marko Mäkelä <marko.makela@mariadb.com>
Date: Sun Nov 17 20:04:11 2019 +0200

Engine
commit 7c6a086cfb54b8bbd500efb41f34c9fa1ed03ca1
Merge: f291d88 1a94d53
Author: Roman Nozdrin <drrtuy@gmail.com>
Date: Mon Nov 18 12:11:30 2019 +0300

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