Open topic with navigation
Table partitions and storage groups are currently only supported under "unmanaged" databases. Use the incremental restart command to restart failed nodes into a running database.
When you create a database, NuoDB maps the
UNPARTITIONED storage group to each of the database’s storage managers. This is the case whether you use Automation Console to create the database or the NuoDB Manager
create database command.
While you can add storage groups and map them to particular storage managers, these modifications are not included as part of the automation of database processes. If the mapped-to storage manager terminates and the enforcer starts a new storage manager then the storage group mapping is not in effect for the new storage manager. Again, it does not matter whether you use Automation Console or NuoDB Manager to add the storage group.
The default behavior is that NuoDB creates the
ALL storage group for managed databases. However, it is not currently possible to manage (create, delete, map to an SM) the
ALL storage group in Automation Console.
If you invoke the NuoDB Manager
start process sm command, and specify the
storage-group all option, the enforcer no longer manages that storage manager. For example, if a database requires a minimum of two storage managers then the enforcer will ensure that there are two storage managers in addition to the storage manager that was started with the
storage-group all option.
Automation Console includes preview support for storage groups. You can use Automation Console to read information about storage groups and the storage manager hosts they are mapped to. However, Automation Console features for creating a storage group and for mapping a storage group to a storage manager on a particular host are incomplete and not supported for any use at this time.