This page describes how to replace your MemSQL license in a cluster managed by MemSQL Ops.
You should not use MemSQL-Ops license capacity (in RAM) as a source of truth if you have a newer unit-based license, because in our unit-based model, only leaf nodes are counted towards your license capacity limit; however, MemSQL-Ops will still count aggregators in its RAM calculation. As a result, it is expected that you might see an over-capacity warning in the Ops UI.
Using MemSQL Ops With Internet Access
In MemSQL Ops, navigate to Settings > Licenses. From that screen, you can add a new MemSQL license. MemSQL Ops will then update all nodes in your MemSQL cluster asynchronously to use the new license.
Or you can use the CLI LICENSE-ADD command to add a new license:
$ memsql-ops license-add --license-key <license key>
Using MemSQL Ops Without Internet Access
If you need to replace your MemSQL license and you do not have internet access, you will have to use the <license-file> argument instead of the above <license key> argument. For this to work, the license file will need to be on the host with the primary memsql-ops agent.
Use memsql-ops agent-list to check which node is the primary agent.
Then use the following command to add a new license:
memsql-ops license-add --license-file </path/to/file>
Without MemSQL Ops
This process is configuration error prone and we recommend that you use MemSQL Ops to update your license instead. Only use this option if MemSQL Ops is unavailable.
- On each node in your cluster, replace the existing license in <MEMSQL_HOME>/lib with your new license.
- On each node in your cluster, run:
$ sudo service memsql update-license <path to new license>
MemSQL Ops does not allow the addition of 3.2 licenses into MemSQL 4+ nodes.
MemSQL licenses issued before the MemSQL 4 launch may still work with MemSQL 4. That said, we recommend that users update their license to a new MemSQL license when possible.
If you need a new license, contact sales@memsql.com.
