Increase the capacity of a Managed Lustre instance

You can increase the storage capacity of your Managed Lustre instance. Capacity cannot be decreased.

To increase the capacity of your Managed Lustre instance, do the following:

  • Determine your new capacity.
  • Use the Google Cloud console or the Google Cloud CLI to update the instance's capacity.
  • Monitor the update. You can continue to use your instance while the update operation is taking place.

Calculate your new capacity

You can update an instance's capacity up to the maximum value allowed for its performance tier. These values are as follows:

Tier Min Capacity Max Capacity Step Size
1000 MBps per TiB
18,000 GiB 954,000 GiB (~1 PiB) 9,000 GiB
500 MBps per TiB
36,000 GiB 1,908,000 GiB (~2 PiB) 18,000 GiB
250 MBps per TiB
72,000 GiB 3,816,000 GiB (~4 PiB) 36,000 GiB
125 MBps per TiB
144,000 GiB 7,632,000 GiB (~8 PiB) 72,000 GiB

The updated capacity must be a multiple of the step size.

Your Google Cloud project has system limits and quotas that affect the available capacity per Virtual Private Cloud (VPC) network per zone. You may need to request additional quota before increasing your instance's capacity. See the Quotas and limits for details.

Update the instance capacity

You can use the Google Cloud console or the Google Cloud CLI to update the instance's capacity.

Google Cloud console

  1. Go to the Managed Lustrepage in the Google Cloud console.

    Go to Managed Lustre

  2. Click the Instance nameof the instance to update. The instance overview page is displayed.

  3. Click Edit.

  4. Enter the new storage capacity value. The value must be equal to or less than the maximum allowed capacity, and must be a multiple of the step size. See Calculate your new capacity for these values.

  5. Click Submit.

gcloud

Use the gcloud lustre instances update command to increase your instance's storage capacity:

 gcloud lustre instances update INSTANCE_NAME 
\
  --location= LOCATION 
\
  --capacity-gib= NEW_CAPACITY 
 

Where:

  • INSTANCE_NAME is the instance to update.
  • LOCATION is the zone in which the instance resides.
  • NEW_CAPACITY is the new storage capacity for this instance in gibibytes (GiB). The value cannot exceed the maximum allowed capacity and must be a multiple of the step size. See Calculate your new capacity for these values.

REST

To update an instance using the REST API, send a PATCH request to its specific endpoint:

  PATCH 
  
 h 
 tt 
 ps 
 : 
 //lustre.googleapis.com/v1/projects/ PROJECT_ID 
/locations/ ZONE 
/instances/ INSTANCE_NAME 
?updateMask=capacityGib 
 Au 
 t 
 horiza 
 t 
 io 
 n 
 : 
  
 Bearer 
  
 [ 
 YOUR_ACCESS_TOKEN 
 ] 
 { 
  
 "capacityGib" 
 : 
  
  NEW_CAPACITY 
 
 } 
 

Where the following values must be specified:

  • PROJECT_ID is your Google Cloud project ID.
  • ZONE is the instance's Google Cloud zone.
  • INSTANCE_NAME is the name of the Managed Lustre instance to update.
  • updateMask=capacityGib specifies the field to update. A field will only be overwritten if it is in the mask.
  • NEW_CAPACITY is the new storage capacity for this instance in gibibytes (GiB). The value cannot exceed the maximum allowed capacity and must be a multiple of the step size. See Calculate your new capacity for these values.

See the instances.patch API reference for more details.

Once the update request has been submitted, Managed Lustre checks your available quota. If sufficient quota exists, the instance capacity is increased over a period of time, depending on the size change. Increases can take from 20 minutes to an hour or more.

You can continue to use your instance during the update operation.

View update status

You can view the status of an update request from the following interfaces.

Google Cloud console

  1. Go to the Managed Lustrepage in the Google Cloud console.

    Go to Managed Lustre

  2. Click the instance name in the list. The Instance Detailspage appears, which includes the current status of your instance update request.

gcloud

By default, the gcloud lustre instances update command waits for completion before returning the shell prompt:

 Request issued for: [my-instance]
Waiting for operation [projects/my-project/locations/us-central1-a/operations/operation-1234567890-123] to complete... 

Once complete, the command line displays Updated instance [my-instance] along with the instance details, including the updated capacity.

If you ran the update command with the --async flag, or otherwise need to query the update status from the command line, you can retrieve the operation details to see if the instance has finished updating:

 gcloud  
lustre  
operations  
describe  
 OPERATION_ID 
  
 \ 
  
--location = 
 ZONE 
 

While the instance is updating, the response shows a done: false value. Once complete, done is set to true .

For example:

 $  
gcloud  
lustre  
operations  
describe  
operation-1234567890-123abc456-789def012-a1b2c3d4  
 \ 
  
--location = 
us-central1-a done 
:  
 false 
metadata:  
 '@type' 
:  
type.googleapis.com/google.cloud.lustre.v1.OperationMetadata  
apiVersion:  
v1  
createTime:  
 '2025-08-27T18:13:49.771203623Z' 
  
requestedCancellation:  
 false 
  
target:  
projects/my-project/locations/us-central1-a/instances/my-instance  
verb:  
update
name:  
projects/my-project/locations/us-central1-a/operations/operation-1234567890-123abc456-789def012-a1b2c3d4 

REST

To query the status of an update operation, use the operation ID from the response. The operation ID has the following format:

  • operation-1234567890123-6127783ad26ea-88913969-02748053

Send a request to the following endpoint:

 GET https://lustre.googleapis.com/v1/projects/ PROJECT_ID 
/locations/ ZONE 
/operations/ OPERATION_ID 
Authorization: Bearer 

If successful, the response body contains an instance of Operation .

Performance after increasing capacity

A Managed Lustre instance's maximum throughput is determined by its storage capacity and performance tier. Increasing the storage capacity of an existing instance increases its maximum throughput as well.

The performance increase may not be seen until new data has been written. Throughput performance gradually improves as new data is written and redistributed across the additional storage.

Design a Mobile Site
View Site in Mobile | Classic
Share by: