mcs

The MCS Command Line Interface is a unified tool to manage your MCS services

Usage:

    $ mcs [OPTIONS] COMMAND [ARGS]...

Options:

    •   -v, --verbose: Enable verbose logging to console

    •   --help: Show this message and exit.

Commands:

    •   backup: Backup Columnstore and/or MariaDB data.

    •   dbrm_backup: Columnstore DBRM Backup.

    •   restore: Restore Columnstore (and/or MariaDB) data.

    •   dbrm_restore: Restore Columnstore DBRM data.

    •   cskeys: Generate a random AES encryption key and init vector and write them to disk.

    •   cspasswd: Encrypt a Columnstore plaintext password.

    •   bootstrap-single-node: Bootstrap a single node (localhost)...

    •   review: Provides useful functions to review and troubleshoot the MCS cluster.

    •   install_es: [Beta] Install the specified MDB ES version.

    •   help-all: Show help for all commands in man page style.

    •   status: Get status information.

    •   stop: Stop the Columnstore cluster.

    •   start: Start the Columnstore cluster.

    •   restart: Restart the Columnstore cluster.

    •   node: Cluster nodes management.

    •   set: Set cluster parameters.

    •   cluster: MariaDB Columnstore cluster management...

    •   cmapi: Commands related to CMAPI itself.

    •   sentry: Manage Sentry DSN configuration for error...

mcs backup

Backup Columnstore and/or MariaDB data.

Usage:

    $ mcs backup [OPTIONS]

Options:

    •   -bl, --backup-location TEXT: What directory to store the backups on this machine or the target machine. Consider write permissions of the scp user and the user running this script. Mariadb-backup will use this location as a tmp dir for S3 and remote backups temporarily. Example: /mnt/backups/

    •   -bd, --backup-destination TEXT: Are the backups going to be stored on the same machine this script is running on or another server - if Remote you need to setup scp=Options: "Local" or "Remote"

    •   -scp, --secure-copy-protocol TEXT: Used only if --backup-destination="Remote". The user/credentials that will be used to scp the backup files Example: "⟨centos@192.168.0.1⟩"

    •   -bb, --backup-bucket TEXT: Only used if --storage=S3 Name of the bucket to store the columnstore backups. Example: "s3://my-cs-backups"

    •   -url, --endpoint-url TEXT: Used by on premise S3 vendors. Example: "⟨http://127.0.0.1:8000⟩"

    •   -s, --storage TEXT: What storage topogoly is being used by Columnstore - found in /etc/columnstore/storagemanager.cnf. Options: "LocalStorage" or "S3"

    •   -i, --incremental TEXT: Adds columnstore deltas to an existing full backup. Backup folder to apply increment could be a value or "automostrecent" - the incremental backup applies to last full backup.

    •   -P, --parallel INTEGER: Enables parallel rsync for faster backups, setting the number of simultaneous rsync processes. With -c/--compress, sets the number of compression threads.

    •   -ha, --highavilability: Hint wether shared storage is attached @ below on all nodes to see all data HA LocalStorage ( /var/lib/columnstore/dataX/ ) HA S3 ( /var/lib/columnstore/storagemanager/ )

    •   -f, --config-file TEXT: Path to backup configuration file to load variables from - relative or full path accepted.

    •   -sbrm, --skip-save-brm: Skip saving brm prior to running a backup - ideal for dirty backups.

    •   -spoll, --skip-polls: Skip sql checks confirming no write/cpimports running.

    •   -slock, --skip-locks: Skip issuing write locks - ideal for dirty backups.

    •   -smdb, --skip-mariadb-backup: Skip running a mariadb-backup for innodb data - ideal for incremental dirty backups.

    •   -sb, --skip-bucket-data: Skip taking a copy of the columnstore data in the bucket.

    •   -nb, --name-backup TEXT: Define the name of the backup - default: $(date +%m-%d-%Y)

    •   -c, --compress TEXT: Compress backup in X format - Options: [ pigz ].

    •   -q, --quiet: Silence verbose copy command outputs.

    •   -nv-ssl, --no-verify-ssl: Skips verifying ssl certs, useful for onpremise s3 storage.

    •   -pi, --poll-interval INTEGER: Number of seconds between poll checks for active writes & cpimports.

    •   -pmw, --poll-max-wait INTEGER: Max number of minutes for polling checks for writes to wait before exiting as a failed backup attempt.

    •   -r, --retention-days INTEGER: Retain backups created within the last X days, default 0 == keep all backups.

    •   -aro, --apply-retention-only: Only apply retention policy to existing backups, does not run a backup.

    •   -li, --list: List backups.

    •   --help: Show this message and exit.

mcs dbrm_backup

Columnstore DBRM Backup.

Usage:

    $ mcs dbrm_backup [OPTIONS]

Options:

    •   -i, --interval INTEGER: Number of minutes to sleep when --mode=loop. [default: 90]

    •   -r, --retention-days INTEGER: Retain dbrm backups created within the last X days, the rest are deleted [default: 7]

    •   -bl, --backup-location TEXT: Path of where to save the dbrm backups on disk. [default: /tmp/dbrm_backups]

    •   -m, --mode TEXT: "loop" or "once" ; Determines if this script runs in a forever loop sleeping -i minutes or just once. [default: once]

    •   -nb, --name-backup TEXT: Define the prefix of the backup - default: dbrmbackup+date +%Y%m%d%H%M%S [default: dbrm_backup]

    •   -ssm, --skip-storage-manager: Skip backing up storagemanager directory.

    •   -sbrm, --skip-save-brm: Skip saving BRM prior to running a DBRM backup - ideal for dirty backups.

    •   -slock, --skip-locks: Skip issuing flush read locks to dbrms.

    •   -spoll, --skip-polls: Skip polling to confirm locks are released.

    •   -q, --quiet: Silence verbose copy command outputs.

    •   -pi, --poll-interval INTEGER: Number of seconds to wait between polls to confirm.

    •   -pmw, --poll-max-wait INTEGER: Max number of minutes for polling checks for writes to wait before exiting as a failed dbrm backup attempt.

    •   -li, --list: List backups.

    •   --help: Show this message and exit.

mcs restore

Restore Columnstore (and/or MariaDB) data.

Usage:

    $ mcs restore [OPTIONS]

Options:

    •   -l, --load TEXT: What date folder to load from the backup_location.

    •   -bl, --backup-location TEXT: Where the backup to load is found. Example: /mnt/backups/ [default: /tmp/backups/]

    •   -bd, --backup_destination TEXT: Is this backup on the same or remote server compared to where this script is running. Options: "Local" or "Remote" [default: Local]

    •   -scp, --secure-copy-protocol TEXT: Used only if --backup-destination=RemoteThe user/credentials that will be used to scp the backup files.Example: "⟨centos@10.14.51.62⟩"

    •   -bb, --backup-bucket TEXT: Only used if --storage=S3 Name of the bucket to store the columnstore backups. Example: "s3://my-cs-backups"

    •   -url, --endpoint-url TEXT: Used by on premise S3 vendors. Example: "⟨http://127.0.0.1:8000⟩"

    •   -s, --storage TEXT: What storage topogoly is being used by Columnstore - found in /etc/columnstore/storagemanager.cnf. Options: "LocalStorage" or "S3" [default: LocalStorage]

    •   -dbs, --dbroots INTEGER: Number of database roots in the backup. [default: 1]

    •   -pm, --nodeid TEXT: Forces the handling of the restore as this node as opposed to whats detected on disk.

    •   -nb, --new-bucket TEXT: Defines the new bucket to copy the s3 data to from the backup bucket. Use -nb if the new restored cluster should use a different bucket than the backup bucket itself.

    •   -nr, --new-region TEXT: Defines the region of the new bucket to copy the s3 data to from the backup bucket.

    •   -nk, --new-key TEXT: Defines the aws key to connect to the new_bucket.

    •   -ns, --new-secret TEXT: Defines the aws secret of the aws key to connect to the new_bucket.

    •   -P, --parallel INTEGER: Determines number of decompression and mdbstream threads. Ignored if "-c/--compress" argument not set. [default: 4]

    •   -ha, --highavilability: Flag for high available systems (meaning shared storage exists supporting the topology so that each node sees all data)

    •   -cont, --continue: This acknowledges data in your --newbucket is ok to delete when restoring S3. When set to true skips the enforcement that newbucket should be empty prior to starting a restore.

    •   -f, --config-file TEXT: Path to backup configuration file to load variables from - relative or full path accepted.

    •   -smdb, --skip-mariadb-backup: Skip restoring mariadb server via mariadb-backup - ideal for only restoring columnstore.

    •   -sb, --skip-bucket-data: Skip restoring columnstore data in the bucket - ideal if looking to only restore mariadb server.

    •   -c, --compress TEXT: Hint that the backup is compressed in X format. Options: [ pigz ].

    •   -q, --quiet: Silence verbose copy command outputs.

    •   -nv-ssl, --no-verify-ssl: Skips verifying ssl certs, useful for onpremise s3 storage.

    •   -li, --list: List backups.

    •   --help: Show this message and exit.

mcs dbrm_restore

Restore Columnstore DBRM data.

Usage:

    $ mcs dbrm_restore [OPTIONS]

Options:

    •   -bl, --backup-location TEXT: Path of where dbrm backups exist on disk. [default: /tmp/dbrm_backups]

    •   -l, --load TEXT: Name of the directory to restore from -bl

    •   -ns, --no-start: Do not attempt columnstore startup post dbrm_restore.

    •   -sdbk, --skip-dbrm-backup: Skip backing up dbrms before restoring.

    •   -ssm, --skip-storage-manager: Skip backing up storagemanager directory.

    •   -li, --list: List backups.

    •   --help: Show this message and exit.

mcs cskeys

This utility generates a random AES encryption key and init vector and writes them to disk. The data is written to the file '.secrets', in the specified directory. The key and init vector are used by the utility 'cspasswd' to encrypt passwords used in Columnstore configuration files, as well as by Columnstore itself to decrypt the passwords.

WARNING: Re-creating the file invalidates all existing encrypted passwords in the configuration files.

Usage:

    $ mcs cskeys [OPTIONS] [DIRECTORY]

Arguments:

    •   [DIRECTORY]: The directory where to store the file in. [default: /var/lib/columnstore]

Options:

    •   -u, --user TEXT: Designate the owner of the generated file. [default: mysql]

    •   --help: Show this message and exit.

mcs cspasswd

Encrypt a Columnstore plaintext password using the encryption key in the key file.

Usage:

    $ mcs cspasswd [OPTIONS]

Options:

    •   --password TEXT: Password to encrypt/decrypt [required]

    •   --decrypt: Decrypt an encrypted password instead.

    •   --help: Show this message and exit.

mcs bootstrap-single-node

Bootstrap a single node (localhost) Columnstore instance.

Usage:

    $ mcs bootstrap-single-node [OPTIONS]

Options:

    •   --api-key TEXT: API key to set.

    •   --help: Show this message and exit.

mcs review

This script performs various maintenance and diagnostic tasks for MariaDB ColumnStore, including log archiving, extent map backups, schema and table testing, directory and ownership checks, extent map validation, S3 storage comparison, process management, table synchronization, port availability checks, stack dumps, cleanup of rollback fragments, and graceful process termination.

If database is up, this script will connect as root@localhost via socket.

Usage:

    $ mcs review [OPTIONS]

Options:

    •   --version: Only show the header with version information.

    •   --logs: Create a compressed archive of logs for MariaDB Support Ticket

    •   --path TEXT: Define the path for where to save files/tarballs and outputs of this script.

    •   --backupdbrm: Takes a compressed backup of extent map files in dbrm directory.

    •   --testschema: Creates a test schema, tables, imports, queries, drops schema.

    •   --testschemakeep: Creates a test schema, tables, imports, queries, does not drop.

    •   --ldlischema: Using ldli, creates test schema, tables, imports, queries, drops schema.

    •   --ldlischemakeep: Using ldli, creates test schema, tables, imports, queries, does not drop.

    •   --emptydirs: Searches /var/lib/columnstore for empty directories.

    •   --notmysqldirs: Searches /var/lib/columnstore for directories not owned by mysql.

    •   --emcheck: Checks the extent map for orphaned and missing files.

    •   --s3check: Checks the extent map against S3 storage.

    •   --pscs: Adds the pscs command. pscs lists running columnstore processes.

    •   --schemasync: Fix out-of-sync columnstore tables (CAL0009).

    •   --tmpdir: Ensure owner of temporary dir after reboot (MCOL-4866 & MCOL-5242).

    •   --checkports: Checks if ports needed by Columnstore are opened.

    •   --eustack: Dumps the stack of Columnstore processes.

    •   --clearrollback: Clear any rollback fragments from dbrm files.

    •   --killcolumnstore: Stop columnstore processes gracefully, then kill remaining processes.

    •   --color TEXT: print headers in color. Options: prefix color with l for light.

    •   --help: Show this message and exit.

mcs install_es

[Beta] Install the specified MDB ES version. If the version is 'latest', it will upgrade to the latest tested version available for your OS.

Usage:

    $ mcs install_es [OPTIONS]

Options:

    •   --token TEXT: ES API Token to use for the upgrade. [required]

    •   -v, --version TEXT: ES version to upgdate.

    •   --ignore-mismatch: Proceed even if nodes report different installed package versions (use majority as baseline).

    •   --skip-cmapi: Skip CMAPI upgrade/install entirely. Use when CMAPI does not need to be updated (e.g. custom/latest CMAPI version already installed).

    •   --allow-cmapi-downgrade: Allow CMAPI to be downgraded when performing a downgrade. By default, CMAPI will NOT be downgraded to prevent meeting an already fixed issues and loss the new features.

    •   --help: Show this message and exit.

mcs help-all

Show help for all commands in man page style.

Usage:

    $ mcs help-all [OPTIONS]

mcs status

Get status information.

Usage:

    $ mcs status [OPTIONS]

Options:

    •   -h, --human-readable: Output cluster status in human-readable text instead of JSON.

    •   --help: Show this message and exit.

mcs stop

Stop the Columnstore cluster.

Usage:

    $ mcs stop [OPTIONS]

Options:

    •   -i, --interactive / -no-i, --no-interactive: Use this option on active cluster as interactive stop waits for current writes to complete in DMLProc before shutting down. Ensuring consistency, preventing data loss of active writes. [default: no-interactive]

    •   -t, --timeout INTEGER: Time in seconds to wait for DMLproc to gracefully stop.Warning: Low wait timeout values could result in data loss if the cluster is very active.In interactive mode means delay time between promts. [default: 15]

    •   --help: Show this message and exit.

mcs start

Start the Columnstore cluster.

Usage:

    $ mcs start [OPTIONS]

Options:

    •   --help: Show this message and exit.

mcs restart

Restart the Columnstore cluster.

Usage:

    $ mcs restart [OPTIONS]

Options:

    •   --help: Show this message and exit.

mcs node

Cluster nodes management.

Usage:

    $ mcs node [OPTIONS] COMMAND [ARGS]...

Options:

    •   --help: Show this message and exit.

Commands:

    •   add: Add nodes to the Columnstore cluster.

    •   remove: Remove nodes from the Columnstore cluster.

  mcs node add

Add nodes to the Columnstore cluster.

Usage:

    $ mcs node add [OPTIONS]

Options:

    •   --node TEXT: node IP, name or FQDN. Can be used multiple times to add several nodes at a time. [required]

    •   --read-replica: Add node (or nodes, if more than one is passed) as read replicas.

    •   --help: Show this message and exit.

  mcs node remove

Remove nodes from the Columnstore cluster.

Usage:

    $ mcs node remove [OPTIONS]

Options:

    •   --node TEXT: node IP, name or FQDN. Can be used multiple times to remove several nodes at a time. [required]

    •   --help: Show this message and exit.

mcs set

Set cluster parameters.

Usage:

    $ mcs set [OPTIONS] COMMAND [ARGS]...

Options:

    •   --help: Show this message and exit.

Commands:

    •   mode: Set Columnstore cluster mode.

    •   api-key: Set API key for communication with cluster...

    •   log-level: Set logging level on all cluster nodes for...

  mcs set mode

Set Columnstore cluster mode.

Usage:

    $ mcs set mode [OPTIONS]

Options:

    •   --mode TEXT: cluster mode to set. "readonly" or "readwrite" are the only acceptable values. [required]

    •   --help: Show this message and exit.

  mcs set api-key

Set API key for communication with cluster nodes via API.

WARNING: this command will affect API key value on all cluster nodes.

Usage:

    $ mcs set api-key [OPTIONS]

Options:

    •   --key TEXT: API key to set. [required]

    •   --help: Show this message and exit.

  mcs set log-level

Set logging level on all cluster nodes for develop purposes.

WARNING: this could dramatically affect the number of log lines.

Usage:

    $ mcs set log-level [OPTIONS]

Options:

    •   --level TEXT: Logging level to set. [required]

    •   --help: Show this message and exit.

mcs cluster

MariaDB Columnstore cluster management command line tool.

Usage:

    $ mcs cluster [OPTIONS] COMMAND [ARGS]...

Options:

    •   --help: Show this message and exit.

Commands:

    •   status: Get status information.

    •   stop: Stop the Columnstore cluster.

    •   start: Start the Columnstore cluster.

    •   restart: Restart the Columnstore cluster.

    •   node: Cluster nodes management.

    •   set: Set cluster parameters.

  mcs cluster status

Get status information.

Usage:

    $ mcs cluster status [OPTIONS]

Options:

    •   -h, --human-readable: Output cluster status in human-readable text instead of JSON.

    •   --help: Show this message and exit.

  mcs cluster stop

Stop the Columnstore cluster.

Usage:

    $ mcs cluster stop [OPTIONS]

Options:

    •   -i, --interactive / -no-i, --no-interactive: Use this option on active cluster as interactive stop waits for current writes to complete in DMLProc before shutting down. Ensuring consistency, preventing data loss of active writes. [default: no-interactive]

    •   -t, --timeout INTEGER: Time in seconds to wait for DMLproc to gracefully stop.Warning: Low wait timeout values could result in data loss if the cluster is very active.In interactive mode means delay time between promts. [default: 15]

    •   --help: Show this message and exit.

  mcs cluster start

Start the Columnstore cluster.

Usage:

    $ mcs cluster start [OPTIONS]

Options:

    •   --help: Show this message and exit.

  mcs cluster restart

Restart the Columnstore cluster.

Usage:

    $ mcs cluster restart [OPTIONS]

Options:

    •   --help: Show this message and exit.

  mcs cluster node

Cluster nodes management.

Usage:

    $ mcs cluster node [OPTIONS] COMMAND [ARGS]...

Options:

    •   --help: Show this message and exit.

Commands:

    •   add: Add nodes to the Columnstore cluster.

    •   remove: Remove nodes from the Columnstore cluster.

  mcs cluster node add

Add nodes to the Columnstore cluster.

Usage:

    $ mcs cluster node add [OPTIONS]

Options:

    •   --node TEXT: node IP, name or FQDN. Can be used multiple times to add several nodes at a time. [required]

    •   --read-replica: Add node (or nodes, if more than one is passed) as read replicas.

    •   --help: Show this message and exit.

  mcs cluster node remove

Remove nodes from the Columnstore cluster.

Usage:

    $ mcs cluster node remove [OPTIONS]

Options:

    •   --node TEXT: node IP, name or FQDN. Can be used multiple times to remove several nodes at a time. [required]

    •   --help: Show this message and exit.

  mcs cluster set

Set cluster parameters.

Usage:

    $ mcs cluster set [OPTIONS] COMMAND [ARGS]...

Options:

    •   --help: Show this message and exit.

Commands:

    •   mode: Set Columnstore cluster mode.

    •   api-key: Set API key for communication with cluster...

    •   log-level: Set logging level on all cluster nodes for...

  mcs cluster set mode

Set Columnstore cluster mode.

Usage:

    $ mcs cluster set mode [OPTIONS]

Options:

    •   --mode TEXT: cluster mode to set. "readonly" or "readwrite" are the only acceptable values. [required]

    •   --help: Show this message and exit.

  mcs cluster set api-key

Set API key for communication with cluster nodes via API.

WARNING: this command will affect API key value on all cluster nodes.

Usage:

    $ mcs cluster set api-key [OPTIONS]

Options:

    •   --key TEXT: API key to set. [required]

    •   --help: Show this message and exit.

  mcs cluster set log-level

Set logging level on all cluster nodes for develop purposes.

WARNING: this could dramatically affect the number of log lines.

Usage:

    $ mcs cluster set log-level [OPTIONS]

Options:

    •   --level TEXT: Logging level to set. [required]

    •   --help: Show this message and exit.

mcs cmapi

Commands related to CMAPI itself.

Usage:

    $ mcs cmapi [OPTIONS] COMMAND [ARGS]...

Options:

    •   --help: Show this message and exit.

Commands:

    •   is-ready: Check CMAPI is ready to handle requests.

    •   config: Manage CMAPI configuration.

  mcs cmapi is-ready

Check CMAPI is ready to handle requests.

Usage:

    $ mcs cmapi is-ready [OPTIONS]

Options:

    •   --node TEXT: Which node to check the CMAPI is ready to handle requests. [default: 127.0.0.1]

    •   --help: Show this message and exit.

  mcs cmapi config

Manage CMAPI configuration.

Usage:

    $ mcs cmapi config [OPTIONS] COMMAND [ARGS]...

Options:

    •   --help: Show this message and exit.

Commands:

    •   set: Set CMAPI configuration on all nodes.

  mcs cmapi config set

Set CMAPI configuration on all nodes.

Usage:

    $ mcs cmapi config set [OPTIONS]

Options:

    •   --sampling-interval-seconds INTEGER RANGE: Failover sampling interval in seconds. [x>=1]

    •   --help: Show this message and exit.

mcs sentry

Manage Sentry DSN configuration for error tracking.

Usage:

    $ mcs sentry [OPTIONS] COMMAND [ARGS]...

Options:

    •   --help: Show this message and exit.

Commands:

    •   show: Show current Sentry DSN configuration.

    •   enable: Enable Sentry error tracking with the...

    •   disable: Disable Sentry error tracking by removing...

  mcs sentry show

Show current Sentry DSN configuration.

Usage:

    $ mcs sentry show [OPTIONS]

Options:

    •   --help: Show this message and exit.

  mcs sentry enable

Enable Sentry error tracking with the provided DSN.

Usage:

    $ mcs sentry enable [OPTIONS] DSN

Arguments:

    •   DSN: Sentry DSN URL to enable for error tracking. [required]

Options:

    •   -e, --environment TEXT: Sentry environment name (default: development). [default: development]

    •   --help: Show this message and exit.

  mcs sentry disable

Disable Sentry error tracking by removing the configuration.

Usage:

    $ mcs sentry disable [OPTIONS]

Options:

    •   --help: Show this message and exit.