Skip to end of metadata
Go to start of metadata

Licensing Overview

ClustrixDB must have a valid license in order to run. This license specifies:

  1. The maximum number of nodes allowed in the cluster
  2. The maximum number of cores that will be utilized by ClustrixDB
    1. ClustrixDB automatically determines the number of cores available on each server:
      1. On bare metal systems, ClustrixDB will attempt to enable the same number of physical cores as licensed and utilize hyperthreading if available (up to 32 cores)
      2. For virtualized systems, ClustrixDB will enable the number of cores available (included hyperthreaded, up to 32 cores)

If the cluster does not have a valid or current license, the database will operate in read-only mode.

Obtaining a License

To obtain a license key, please contact Clustrix Sales. If you encounter any problems or issues while using these instructions, please contact Clustrix Support.

Enterprise Licenses are based on a cluster_id, which is a machine-generated unique identifier for your cluster. The value for cluster_id is available by providing the following at a MySQL prompt:

sql> select @@cluster_id;

Licensing a New ClustrixDB Database

Licenses are delivered as long strings of text that begin and end in { } braces. Whenever entering a license key, be sure to include the braces too.

Specify the license key at the command line:

SQL to set License Key
sql> set global license = 'license_key_including_braces';

Expanding or Extending Your License

Contact Clustrix Sales when you want to add nodes, add cores, or renew your license. Clustrix Sales will provide you with a new license key. 

If you are changing to a license that uses more cores, the CPUs are enabled as soon as the system detects a change in licensing.

Changing a license to one that uses fewer cores is a two-step process:

  1. Edit the CPU_CORES value in clxnode.conf on every node.
  2. Apply the license as shown below.

License Expiration

Beginning 30 days prior to expiration, the database will issue an alert that the license is about to expire. This alert is sent weekly until the license has expired. Once the license has expired, alerts will be sent daily and the database will automatically enter license-expired mode and become read only. 

Checking the Status of Your License

To check the status of your license, run the following query to determine whether your license is valid:

sql> select system.license_valid();

If your license is not valid, the results of the following query can tell you why:

sql> select system.license_status();
  • No labels