update_table_replica_auto_scaling
¶
update_table_replica_auto_scaling(
table_name: TableArn,
*,
config_overrides: Optional[DynamoDBClientConfig] = None,
global_secondary_index_updates: Optional[
GlobalSecondaryIndexAutoScalingUpdateList
] = None,
provisioned_write_capacity_auto_scaling_update: Optional[
AutoScalingSettingsUpdate
] = None,
replica_updates: Optional[ReplicaAutoScalingUpdateList] = None,
) -> UpdateTableReplicaAutoScalingOutput
Updates auto scaling settings on your global tables at once.
Parameters:
-
global_secondary_index_updates(Optional[GlobalSecondaryIndexAutoScalingUpdateList], default:None) –Represents the auto scaling settings of the global secondary indexes of the replica to be updated.
-
table_name(TableArn) –The name of the global table to be updated. You can also provide the Amazon Resource Name (ARN) of the table in this parameter.
-
replica_updates(Optional[ReplicaAutoScalingUpdateList], default:None) –Represents the auto scaling settings of replicas of the table that will be modified.
Raises:
-
InternalServerError–An error occurred on the server side.
-
LimitExceededException–There is no limit to the number of daily on-demand backups that can be taken.
For most purposes, up to 500 simultaneous table operations are allowed per account. These operations include
CreateTable,UpdateTable,DeleteTable,UpdateTimeToLive,RestoreTableFromBackup, andRestoreTableToPointInTime.When you are creating a table with one or more secondary indexes, you can have up to 250 such requests running at a time. However, if the table or index specifications are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.
There is a soft account quota of 2,500 tables.
GetRecords was called with a value of more than 1000 for the limit request parameter.
More than 2 processes are reading from the same streams shard at the same time. Exceeding this limit may result in request throttling.
-
ResourceInUseException–The operation conflicts with the resource's availability. For example:
-
You attempted to recreate an existing table.
-
You tried to delete a table currently in the
CREATINGstate. -
You tried to update a resource that was already being updated.
When appropriate, wait for the ongoing update to complete and attempt the request again.
-
-
ResourceNotFoundException–The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be
ACTIVE. -
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_dynamodb/_services/dynamo_db.py
4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 | |