Skip to content

Commit a6386ad

Browse files
authored
Merge pull request #241970 from spelluru/patch-193
Update storage-checkpoint-store-recommendations.md
2 parents 0322b05 + 9ea501f commit a6386ad

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

articles/event-hubs/includes/storage-checkpoint-store-recommendations.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ Follow these recommendations when using Azure Blob Storage as a checkpoint store
1515
- Use a separate container for each processor group. You can use the same storage account, but use one container per each group.
1616
- Don't use the container for anything else, and don't use the storage account for anything else.
1717
- Storage account should be in the same region as the deployed application is located in. If the application is on-premises, try to choose the closest region possible.
18-
- Ensure the storage account doesn't have soft delete enabled as it's not supported for the checkpoint store. Soft delete can cause serious delays.
19-
- Ensure the storage account doesn't have versioning enabled as it's supported for the checkpoint store. Soft delete can cause serious delays.
20-
- Don't use a hierarchical storage (Azure Data Lake Storage Gen 2) as a checkpoint store.
18+
19+
On the **Storage account** page in the Azure portal, in the **Blob service** section, ensure that the following settings are disabled.
20+
21+
- Hierarchical namespace
22+
- Blob soft delete
23+
- Versioning
24+

0 commit comments

Comments
 (0)