如何 debug/troubleshoot Azure Cosmos DB 上的元数据 DTU 节流 (Table API)？

Question

我们正在使用 Azure cosmos DB 来保存作业处理管道的状态信息。为此，我们使用 table API 和相应的 SDK。最近发现系统经常运行变成429 – Request rate is too large 错误。我们的交易 DTU 利用率远低于 table 上配置的最大值，但我们注意到在指标选项卡下，枚举 table 等操作使用的系统 DTU 正在耗尽，因此 429。

我们最初的修复方法是删除“CreateIfNotExists”方法调用，帮助修复了一段时间，但最近我们又开始运行解决这个问题（尽管不像以前那么频繁）。 debug/troubleshoot 很难做到这一点，因为我找不到足够的文档来说明哪个 SDK 方法调用耗尽了这个不可扩展的资源。我已经在我们的 CosmosDB 实例上启用了日志记录，但我不确定我在日志中寻找什么来解决这个问题

这是我们用来与 Azure Cosmos DB 交互的单例 class

public class CosmosDbTableFacade : ICosmosDbTableFacade
{
        /// <summary>
        /// Initializes a new instance of the <see cref="CosmosDbTableFacade"/> class.
        /// </summary>
        /// <param name="connectionString">
        /// The connection string.
        /// </param>
        /// <param name="tableName">
        /// The table name.
        /// </param>
        public CosmosDbTableFacade(string connectionString)
        {
            var storageAccount = CloudStorageAccount.Parse(connectionString);
            this.CosmosTableClient = storageAccount.CreateCloudTableClient();
        }

        /// <summary>
        /// Gets or sets the cosmos table.
        /// </summary>
        public CloudTableClient CosmosTableClient { get; set; }

        /// <summary>
        /// The execute async.
        /// </summary>
        /// <param name="tableName">
        /// The table Name.
        /// </param>
        /// <param name="operation">
        /// The operation.
        /// </param>
        /// <returns>
        /// The <see cref="Task"/>.
        /// </returns>
        public Task<TableResult> ExecuteAsync(string tableName, TableOperation operation)
        {
            var table = this.CosmosTableClient.GetTableReference(tableName);
            return table.ExecuteAsync(operation);
        }

        /// <summary>
        /// The execute query segmented async.
        /// </summary>
        /// <param name="tableName">
        /// The table name.
        /// </param>
        /// <param name="query">
        /// The query.
        /// </param>
        /// <param name="continuationToken">
        /// The continuation token.
        /// </param>
        /// <returns>
        /// The <see cref="Task"/> which returns the list of entities.
        /// </returns>
        public Task<TableQuerySegment<DynamicTableEntity>> ExecuteQuerySegmentedAsync(string tableName, TableQuery query, TableContinuationToken continuationToken)
        {
            var table = this.CosmosTableClient.GetTableReference(tableName);
            return table.ExecuteQuerySegmentedAsync(query, continuationToken);
        }
}

以下代码段列出了我们正在使用的不同查询 -

public async Task InsertOrMergeEntityAsync<T>(string tableName, T entity)
            where T : TableEntity
{
            var insertOrMergeOperation = TableOperation.InsertOrMerge(entity);
            var result = await this.CosmosDbTableFacade.ExecuteAsync(tableName, insertOrMergeOperation).ConfigureAwait(false);
            ValidateCosmosTableResult(result, "Failed to write to Cosmos Table");
}

public async Task<T> GetEntityAsync<T>(string tableName, string partitionKey, string rowKey)
            where T : TableEntity
{
            var retrieveOperation = TableOperation.Retrieve<T>(partitionKey, rowKey);
            TableResult result = await this.CosmosDbTableFacade.ExecuteAsync(tableName, retrieveOperation).ConfigureAwait(false);
            ValidateCosmosTableResult(result, "Failed to read from Cosmos Table");
            return result.Result as T;
}

public async Task<IEnumerable<T>> GetEntitiesAsync<T>(string tableName, string filterCondition)
            where T : TableEntity
{
            var query = new TableQuery().Where(filterCondition);
            var continuationToken = default(TableContinuationToken);
            var results = new List<T>();
            do
            {
                var currentQueryResults = await this.CosmosDbTableFacade.ExecuteQuerySegmentedAsync(tableName, query, continuationToken).ConfigureAwait(false);
                results.AddRange(currentQueryResults.Select(currentQueryResult =>
                    {
                        var currentEntity = TableEntity.ConvertBack<T>(currentQueryResult.Properties, null);
                        currentEntity.RowKey = currentQueryResult.RowKey;
                        currentEntity.PartitionKey = currentQueryResult.PartitionKey;
                        currentEntity.Timestamp = currentQueryResult.Timestamp;
                        currentEntity.ETag = currentQueryResult.ETag;
                        return currentEntity;
                    }));
                continuationToken = currentQueryResults.ContinuationToken;
            }
            while (continuationToken != null);

            return results;
}

下面最后一个方法中的过滤器，包含一个分区键和一个自定义列

Answer 1

对于任何运行遇到类似问题的人来说，在我的案例中元数据 DTU 节流的根本原因是：GetTableReference(tableName)方法（通过将该行移动到启动代码并监视 DTU 利用率来部署更改来找到）。我有这个以便我可以在运行时动态指向 table 到 read/write 到哪个，但由于这是消耗元数据 DTU，我更改了我的代码以使用单例作为 table 引用.

如何 debug/troubleshoot Azure Cosmos DB 上的元数据 DTU 节流 (Table API)？

How to debug/troubleshoot metadata DTU throttling on Azure Cosmos DB (Table API)?

throttling

azure

azure-cosmosdb

azure-cosmosdb-tables

http-status-code-429