This page describes how to create, list, edit, and delete Spanner instances.
Create an instance
You can create an instance with the Google Cloud console, the Google Cloud CLI, or client libraries. You can also create an instance with a custom instance configuration by adding optional read-only replicas.
Console
In the Google Cloud console, go to the Spanner Instances page.
Click Create instance.
In the Select an edition section, select a Spanner edition.
If you want to compare the specifications between the different editions, then click Compare editions. For more information, see the Spanner editions overview.
Click Continue.
In the Name your instance section, enter an Instance name to display in the Google Cloud console. The instance name must be unique within your Google Cloud project.
Enter an Instance ID to permanently identify your instance. The instance ID must also be unique within your Google Cloud project. You cannot change the instance ID later.
Click Continue.
In the Configure your instance section, under Choose a configuration, select Regional, Dual-region, or Multi-region.
Select a configuration location from the drop-down.
Optional: To add a read-only replica to a Spanner base configuration, first create a custom instance configuration using the Google Cloud CLI. Adding optional read-only replicas to a base configuration is available in the Enterprise edition and Enterprise Plus edition.
Click Continue.
In the Allocate compute capacity section, under Select unit, click one of the following:
- Processing units for small instances.
- Nodes for large instances. A node is 1000 processing units.
For more information, see Compute capacity, nodes and processing units.
Under Choose a scaling mode, click one of the following:
Manual allocation if you want to manually set compute capacity for fixed compute resources and costs.
- Quantity indicates the number of processing units or nodes to use for this instance.
Autoscaling (Preview), to let Spanner automatically add and remove compute capacity. Managed autoscaler is available in the Spanner Enterprise edition and Enterprise Plus edition. For more information about the managed autoscaler, see Managed autoscaler for Spanner. Configure the following managed autoscaler options:
- Minimum indicates the minimum limit to scale down to, depending on the measurement unit that you choose for Compute capacity. For more information, see Determine the minimum limit.
- Maximum indicates the maximum limit to scale up to, depending on the measurement unit that you choose for Compute capacity. For more information, see Determine the maximum limit.
- High priority CPU utilization target indicates the target percentage of high priority CPU to use. For more information, see Determine the CPU utilization target.
- Storage utilization target indicates the target percentage of storage to use. For more information, see Determine the Storage Utilization Target.
Click Create to create the instance.
gcloud
Use the gcloud spanner instances create
command to create an instance. Specify the compute capacity
as the number of nodes or processing units that you want on the instance.
gcloud spanner instances create INSTANCE_ID \ --edition=EDITION \ --config=INSTANCE_CONFIG \ --description=INSTANCE_DESCRIPTION \ --nodes=NODE_COUNT
or
gcloud spanner instances create INSTANCE_ID \ --edition=EDITION \ --config=INSTANCE_CONFIG \ --description=INSTANCE_DESCRIPTION \ --processing-units=PROCESSING_UNIT_COUNT
Replace the following:
- INSTANCE-ID: a permanent identifier that is unique within your Google Cloud project. You cannot change the instance ID later.
- INSTANCE-CONFIG: a permanent identifier of your instance
configuration, which defines the geographic location of the instance and
affects how data is replicated. For custom instance configurations, it
starts with
custom-
. For more information, see instance configurations. - INSTANCE_DESCRIPTION: the name to display for the instance in the Google Cloud console. The instance name must be unique within your Google Cloud project.
- NODE-COUNT: the compute capacity of the instance, expressed as a number of nodes. Each node equals 1000 processing units.
- PROCESSING_UNIT_COUNT: the compute capacity of the instance, expressed as a number of processing units. Enter quantities up to 1000 in multiples of 100 (100, 200, 300 and so on) and enter greater quantities in multiples of 1000 (1000, 2000, 3000 and so on). Note: Don't use this parameter if you're creating an instance that you intend to enable with the managed autoscaler later.
Add managed autoscaling (Preview)
You can also create Enterprise edition and
Enterprise Plus edition
instances to use managed autoscaling with the
gcloud beta spanner instances create
command. For more information, see
Managed autoscaler for Spanner.
Use the following command to create an instance with managed autoscaler.
gcloud beta spanner instances create INSTANCE_ID \ --edition=EDITION \ --config=INSTANCE_CONFIG \ --description=INSTANCE_DESCRIPTION \ --autoscaling-min-processing-units=MINIMUM_PROCESSING_UNITS \ --autoscaling-max-processing-units=MAXIMUM_PROCESSING_UNITS \ --autoscaling-high-priority-cpu-target=CPU_PERCENTAGE \ --autoscaling-storage-target=STORAGE_PERCENTAGE
or
gcloud beta spanner instances create INSTANCE_ID \ --edition=EDITION \ --config=INSTANCE_CONFIG \ --description=INSTANCE_DESCRIPTION \ --autoscaling-min-nodes=MINIMUM_NODES \ --autoscaling-max-nodes=MAXIMUM_NODES \ --autoscaling-high-priority-cpu-target=CPU_PERCENTAGE \ --autoscaling-storage-target=STORAGE_PERCENTAGE
Replace the following:
- INSTANCE-ID: a permanent identifier that is unique within your Google Cloud project. You cannot change the instance ID later.
- INSTANCE-CONFIG: a permanent identifier of your instance
configuration, which defines the geographic location of the instance and
affects how data is replicated. For custom instance configurations, it
starts with
custom-
. For more information, see instance configurations. - INSTANCE-DESCRIPTION: the name to display for the instance in the Google Cloud console. The instance name must be unique within your Google Cloud project.
- MINIMUM_PROCESSING_UNITS, MINIMUM_NODES: the minimum number of processing units or nodes when scaling down. For more information, see Determine the minimum limit.
- MAXIMUM_PROCESSING_UNITS, MAXIMUM_NODES: the maximum number of processing units or nodes when scaling up. For more information, see Determine the maximum limit.
- CPU_PERCENTAGE: the target percentage of high priority CPU to use, from 10 to 90%. If you're optimizing for cost, then use a higher percentage. For more information, see Determine the CPU utilization target.
- STORAGE_PERCENTAGE: the target percentage of storage to use, from 10 to 99%. For more information, see Determine the storage utilization target.
Examples for using custom configurations
To create an instance test-instance
in the base regional instance
configuration us-central1
, run:
gcloud spanner instances create test-instance --edition=STANDARD --config=regional-us-central1 \
--description="Test Instance" --nodes=1
To create an instance custom-eur6-instance
in the custom multi-region
instance configuration custom-eur6
, first
create a custom instance configuration.
Then, run:
gcloud spanner instances create custom-eur6-instance --edition=ENTERPRISE_PLUS --config=custom-eur6 \
--description="Instance with custom read-only" --nodes=1
You should see a message similar to the following example after running either one of the previous commands:
Creating instance...done.
C++
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
C#
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Go
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Create an instance with managed autoscaling using Go (Preview)
Java
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Create an instance with managed autoscaling using Java (Preview)
Node.js
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
PHP
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Python
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Ruby
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
List instances
You can show a list of your Spanner instances.
Console
Go to the Spanner Instances page in the Google Cloud console.
The Google Cloud console shows a list of your Spanner instances, along with each instance's ID, display name, configuration, and compute capacity expressed in both processing units and in nodes.
gcloud
Use the gcloud spanner instances list
command:
gcloud spanner instances list
The gcloud CLI prints a list of your Spanner instances, along with each instance's ID, display name, configuration, and compute capacity.
Edit an instance
The following sections explain how to upgrade the edition of your instance, and change an instance's display name and compute capacity. You can't change the instance ID or instance configuration (however, you can move your instance).
Upgrade the edition
You can upgrade your Standard edition instances to a higher-tier edition. Standard edition instances can be upgraded to the Enterprise edition or Enterprise Plus edition. Enterprise edition instances can be upgraded to the Enterprise Plus edition.
Self-service downgrade isn't available. To downgrade the edition of your instance, file a support ticket. For more information, see the Spanner editions FAQs.
Console
Go to the Spanner Instances page in the Google Cloud console.
Click the name of the instance that you want to upgrade.
Click Upgrade next to the edition type.
In the Edition instance page, and under Update edition, select the new higher-tier edition for your instance.
Click Save.
gcloud
Use the gcloud spanner instances update
command to upgrade your instance's edition:
gcloud spanner instances update INSTANCE_ID --edition=EDITION \ [--async]
Replace the following:
- INSTANCE_ID: the permanent identifier for the instance.
- EDITION: specify the new higher-tier edition for your instance. For more information, see the Spanner editions overview.
Optional flags:
--async
: Use this flag if you want your request to return immediately, without waiting for the operation in progress to complete. You can check the status of your request by runninggcloud spanner operations describe
.
Go
Java
Node.js
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Python
To learn how to install and use the client library for Spanner, see Spanner client libraries.
To authenticate to Spanner, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Change the display name
Console
Go to the Spanner Instances page in the Google Cloud console.
Click the name of the instance that you want to rename.
Click Edit instance.
Enter a new instance name. This name must be unique within the Google Cloud project.
Click Save.
gcloud
Use the gcloud spanner instances update
command:
gcloud spanner instances update INSTANCE_ID --description=INSTANCE_NAME
Replace the following:
- INSTANCE_ID: the permanent identifier for the instance.
- INSTANCE_NAME: the name to display for the instance in the Google Cloud console. The instance name must be unique within your Google Cloud project.
Change the compute capacity
You must provision enough compute capacity to keep CPU utilization and storage utilization below the recommended maximums. For more information, see the quotas and limits for Spanner.
There are a few cases in which you can't reduce the compute capacity of an existing instance:
- Removing compute capacity would require your instance to store more than 4 TB of data per 1000 processing units (1 node).
- Based on your historic usage patterns, Spanner has created a large number of splits for your instance's data, and in some rare cases Spanner wouldn't be able to manage the splits after removing compute capacity.
In the latter case, you might try reducing the compute capacity by progressively smaller amounts until you find the minimum capacity that Spanner needs to manage all of the instance's splits. If the instance no longer requires so many splits due to a change in usage patterns, Spanner might eventually merge some splits together and allow you to try reducing the instance's compute capacity further after a week or two.
When removing compute capacity, monitor your CPU utilization and request latencies in Cloud Monitoring to ensure CPU utilization stays under 65% for regional instances and 45% for each region in multi-region instances. You might experience a temporary increase in request latencies while removing compute capacity.
If you want to increase the compute capacity of an instance, your Google Cloud project must have sufficient quota to add the compute capacity. The time it takes for the increase request to complete depends on the size of the request. In most cases, requests complete within a few minutes. On rare occasions, a scale up might take up to an hour to complete.
Console
Go to the Spanner Instances page in the Google Cloud console.
Click the name of the instance that you want to change.
Click Edit Instance.
Change the compute capacity by choosing the measurement units (processing units or nodes) and then entering a quantity. When using processing units, enter quantities up to 1000 in multiples of 100 (100, 200, 300 and so on) and enter greater quantities in multiples of 1000 (1000, 2000, 3000 and so on). Each node equals 1000 processing units.
Click Save.
If you see a dialog that says you have insufficient quota to add compute capacity in this location, follow the instructions to request a higher quota.
gcloud
Use the gcloud spanner instances update
command. When using this command, specify the compute capacity as a
number of nodes or processing units.
gcloud spanner instances update INSTANCE_ID --nodes=NODE_COUNT [--async]
or
gcloud spanner instances update INSTANCE_ID --processing-units=PROCESSING_UNIT_COUNT [--async]
Replace the following:
- INSTANCE_ID: the permanent identifier for the instance.
- NODE_COUNT: the compute capacity of the instance, expressed as a number of nodes. Each node equals 1000 processing units.
- PROCESSING_UNIT_COUNT: the compute capacity of the instance, expressed as a number of processing units. Enter quantities up to 1000 in multiples of 100 (100, 200, 300 and so on) and enter greater quantities in multiples of 1000 (1000, 2000, 3000 and so on).
Optional flags:
--async
: Use this flag if you want your request to return immediately, without waiting for the operation in progress to complete. You can check the status of your request by runninggcloud spanner operations describe
.
Enable or modify managed autoscaler on an instance
The following limitations apply when you add or change the managed autoscaling feature on an existing instance:
- Managed autoscaler is only available in the Enterprise edition or Enterprise Plus edition.
- You can't enable the managed autoscaler on an instance that you are moving.
You can't move an instance while the managed autoscaler is enabled.
Console
Go to the Spanner Instances page in the Google Cloud console.
Click the name of the instance that you want to enable the managed autoscaler on.
Click Edit instance.
Under Configure compute capacity, click Autoscaling.
For Minimum, select the minimum limit to use when scaling down. For more information, see Determine the minimum limit.
For Maximum, select the maximum limit to use when scaling up. For more information, see Determine the maximum limit.
For High priority CPU utilization target, select the percentage of high priority CPU to use. For more information, see Determine the CPU utilization target.
For Storage utilization target, select the percentage of storage to use. For more information, see Determine the storage utilization target.
Click Save.
gcloud
Use the
gcloud beta spanner instances update
command to add the managed autoscaler to an instance. For more information and
limitations, see Google Cloud CLI
flags and limitations.
You can add the managed autoscaler with the following command:
gcloud beta spanner instances update INSTANCE_ID \ --autoscaling-min-processing-units=MINIMUM_PROCESSING_UNITS \ --autoscaling-max-processing-units=MAXIMUM_PROCESSING_UNITS \ --autoscaling-high-priority-cpu-target=CPU_PERCENTAGE \ --autoscaling-storage-target=STORAGE_PERCENTAGE
or
gcloud beta spanner instances update INSTANCE_ID \ --autoscaling-min-processing-units=MINIMUM_NODES \ --autoscaling-max-processing-units=MAXIMUM_NODES \ --autoscaling-high-priority-cpu-target=CPU_PERCENTAGE \ --autoscaling-storage-target=STORAGE_PERCENTAGE
Replace the following:
- INSTANCE_ID: the permanent identifier for the instance.
- MINIMUM_PROCESSING_UNITS, MINIMUM_NODES: the minimum number of processing units or nodes to use when scaling down. For more information, see Determine the minimum limit.
- MAXIMUM_PROCESSING_UNITS, MAXIMUM_NODES: the maximum number of processing units or nodes to use when scaling up. For more information, see Determine the maximum limit.
- CPU_PERCENTAGE: the target percentage of high priority CPU to use, from 10% to 90%. If you're optimizing for cost and don't require low latency on all requests, then use a higher percentage. For more information, see Determine the CPU utilization target.
- STORAGE_PERCENTAGE: the target percentage of storage to use, from 10% to 99%. For more information, see Determine the Storage Utilization Target.
After you add the managed autoscaler to an instance, you can also modify the managed autoscaler settings. For example, if you want to increase the maximum number of processing units to 10000, run the following command:
gcloud beta spanner instances update test-instance \
--autoscaling-max-processing-units=10000
Change an instance from using managed autoscaler to manual scaling
Console
Go to the Spanner Instances page in the Google Cloud console.
Click the name of the instance that you want to disable managed autoscaler on.
Under Choose a scaling mode, click Manual allocation.
Click Save.
gcloud
Use the gcloud beta spanner instances update
command to update the instance.
Use the following command to change an instance from using the managed autoscaler to manual scaling:
gcloud beta spanner instances update INSTANCE_ID \ --processing-units=PROCESSING_UNIT_COUNT
or
gcloud beta spanner instances update INSTANCE_ID \ --nodes=NODE_COUNT
Replace the following:
- INSTANCE_ID: the permanent identifier for the instance.
- NODE_COUNT: the compute capacity of the instance, expressed as a number of nodes. Each node equals 1000 processing units.
- PROCESSING_UNIT_COUNT: the compute capacity of the instance, expressed as a number of processing units. Enter quantities up to 1000 in multiples of 100 (100, 200, 300 and so on) and enter greater quantities in multiples of 1000 (1000, 2000, 3000 and so on).
Label an instance
Labels help organize your resources.
Console
Go to the Spanner Instances page in the Google Cloud console.
Select the checkbox for the instance. The Info panel appears on the right-hand side of the page.
Click the Labels tab in the Info panel. You can then add, delete or update labels for the Spanner instance.
Move an instance
For instructions on how to move your instance from any instance configuration to any other instance configuration, including between regional and multi-regional configurations, see Move an instance.
Delete an instance
You can delete an instance with the Google Cloud console or the Google Cloud CLI.
If you want to delete an instance that has one or more databases with deletion protection enabled, you must first disable the deletion protection on all databases in that instance before you can delete the instance.
Console
Go to the Spanner Instances page in the Google Cloud console.
Click the name of the instance that you want to delete.
Click Delete instance.
Follow the instructions to confirm that you want to delete the instance.
Click Delete.
gcloud
Use the gcloud spanner instances delete
command, replacing INSTANCE_ID with the instance ID:
gcloud spanner instances delete INSTANCE_ID
Stop or restart an instance
Spanner is a fully managed database service which oversees its own underlying tasks and resources, including monitoring and restarting processes when necessary with zero downtime. As there is no need to manually stop or restart a given instance, Spanner does not offer a way to do so.
What's next
- Learn how to insert, update, and delete data with Data Manipulation Language (DML) or the gcloud CLI.
- Grant Identity and Access Management roles for the instance and its databases.
- Understand how to design a Spanner schema.