You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/autopilot-faq.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.topic: conceptual
8
8
ms.date: 12/16/2019
9
9
---
10
10
11
-
# Frequently asked questions about provisioned throughput in autopilot mode (Preview)
11
+
# Frequently asked questions about provisioned throughput in Azure Cosmos DB autopilot mode (Preview)
12
12
With autopilot mode, Azure Cosmos DB will automatically manage and scale the RU/s of your container or database based on usage. This article answers commonly asked questions about autopilot mode.
13
13
14
14
## Frequently asked questions
@@ -26,10 +26,10 @@ Refer to the Azure Cosmos DB [pricing page](https://azure.microsoft.com/pricing/
26
26
Autopilot mode can be enabled on new containers and databases created using the Azure portal.
27
27
28
28
### Is there CLI or SDK support to create containers or databases with autopilot mode?
29
-
Currently, in the preview release, you can only create resources with autopilot mode from the Azure portal. Support for CLI and SDK is not yet available and is planned for GA release.
29
+
Currently, in the preview release, you can only create resources with autopilot mode from the Azure portal. Support for CLI and SDK is not yet available.
30
30
31
31
### Can I enable autopilot on an existing container or a database?
32
-
Currently, you can enable autopilot on new containers and databases when creating them. Support to enable autopilot mode on existing containers and databases is planned for GA. You can migrate existing containers to a new container using [Azure Data Factory](../data-factory/connector-azure-cosmos-db.md) or [change feed](change-feed.md).
32
+
Currently, you can enable autopilot on new containers and databases when creating them. Support to enable autopilot mode on existing containers and databases is not yet available. You can migrate existing containers to a new container using [Azure Data Factory](../data-factory/connector-azure-cosmos-db.md) or [change feed](change-feed.md).
33
33
34
34
### Can I turn off autopilot mode on a container or database?
35
35
Yes, you can turn off autopilot by switching to the 'Manual' option for the provisioned throughput. In the preview release, after switching from autopilot mode to manual mode, you cannot enable autopilot again for the same resource.
@@ -52,7 +52,7 @@ If the storage limit associated with the max throughput of the database or conta
52
52
Autopilot will instantaneously scale up or scale down the RU/s within the minimum and maximum RU/s range, based on incoming traffic. Billing is done at a 1-hour granularity, where you are charged for the highest RU/s in a particular hour.
53
53
54
54
### Can I specify a custom max throughput (RU/s) value for autopilot mode?
55
-
Currently, during the preview release, you can select between [four options](provision-throughput-autopilot.md#autopilot-limits) for max throughput (RU/s). Support for custom, user-specified values of max throughput is planned for GA.
55
+
Currently, during the preview release, you can select between [four options](provision-throughput-autopilot.md#autopilot-limits) for max throughput (RU/s).
56
56
57
57
### Can I increase the max RU/s (move to a higher tier) on the database or container?
58
58
Yes. From the **Scale & Settings** option for your container, or **Scale** option for your database, you can select a higher max RU/s for autopilot. This is an asynchronous scale-up operation that may take sometime to complete (typically 4-6 hours, depending on the RU/s selected) as the service provisions more resources to support the higher scale.
0 commit comments