“意外的操作响应码:0"；执行Azure Table Storage批量删除时 [英] "Unexpected Response Code for Operation: 0" when executing Azure Table Storage batch delete

问题描述

我正在使用适用于.NET的Windows Azure存储库的4.3.0版本.在我的ATS储存库类中，我有几个批处理删除方法，如下所示:

I'm using version 4.3.0 of the Windows Azure Storage libraries for .NET. In my ATS repository class, I have a couple of batch delete methods that look like this:

public async Task DeleteAsync(IEnumerable<T> entities)
{
    await ExecuteAsBatch(entities, (batch, entity) => batch.Delete(entity));
}

private async Task ExecuteAsBatch(IEnumerable<T> entities, Action<TableBatchOperation, T> batchAction)
{
    var byPartition = entities.GroupBy(x => x.PartitionKey).ToList();

    await byPartition.ForEachParallel(async group =>
    {
        // A maximum of 100 actions are allowed per batch job
        var segments = group.ToList().ToSegmentedList(100);
        await segments.ForEachParallel(async segment =>
        {
            var batch = new TableBatchOperation();
            foreach (var entity in segment)
            {
                batchAction(batch, entity);
            }
            await Table.ExecuteBatchAsync(batch);
        }, 10);
    }, 10);
}

在我的代码的其他位置，该DeleteAsync()方法可以正常工作.但是，在某个特定位置，执行批处理时出现此错误消息:

In other places in my code, that DeleteAsync() method works correctly. However, in one particular place, I get this error message when executing the batch:

Unexpected Response Code for Operation: 0

这是呼叫站点:

private async Task MergeAtsOrganizationUserEvents(int organizationId, IEnumerable<CustomerUserEvent> fromEvents, CustomerUser to)
{
    var toDelete = (await fromEvents.SelectParallel(async fromEvent =>
    {
        var pkey = AtsOrganizationUserEventByMinute.GetPartitionKey(organizationId, fromEvent.OccurredOn);
        var rkey = AtsOrganizationUserEventByMinute.GetRowKey(fromEvent.OccurredOn, fromEvent.CustomerUserEventId);
        return await Ats.OrganizationUserEventByMinute.FindByPartitionRowAsync(pkey, rkey);
    })).Where(x => x != null).ToList();

    var toInsert = toDelete
        .Select(x => AtsOrganizationUserEventByMinute.FromBase(x.OrganizationId, x.OccurredOn, x.CookieId,
            to.CustomerUserId, x))
        .ToList();

    try
    {
        await Ats.OrganizationUserEventByMinute.UpsertAsync(toInsert);
        await Ats.OrganizationUserEventByMinute.DeleteAsync(toDelete);
    }
    catch (Exception ex)
    {
        _logger.Error("Unable to merge {0} AtsOrganizationEvents for org {1}, to customer user {2}: {3}",
            toInsert.Count, organizationId, to.CustomerUserId, ex.CompleteMessage());
        throw;
    }
}

上面的UpsertAsync()方法成功，但是DeleteAsync()失败.请注意，它无法删除与FindByPartitionRowAsync()从表中检索到的实体完全相同的实体，因此我无法完全想象它与格式错误的实体或任何类似的实体有什么关系.

The UpsertAsync() method above succeeds, but the DeleteAsync() fails. Note that it fails to delete precisely the same entities that FindByPartitionRowAsync() retrieved from the table, so I can't quite imagine how it could have anything to do with malformed entities or anything of that ilk.

以下是"toDelete"对象之一(以JSON格式)的示例:

Here's an example of one of the "toDelete" objects (in JSON format):

{  
   "CookieId":null,
   "CustomerUserId":185766,
   "CustomerUserEventId":3568687,
   "OrganizationId":4190,
   "EventName":"event1",
   "SessionId":null,
   "OccurredOn":"2014-10-20T18:17:09.9971379Z",
   "UrlId":null,
   "Url":null,
   "ReferrerUrlId":null,
   "ReferrerUrl":null,
   "IsSynthetic":false,
   "IpAddress":null,
   "PartitionKey":"4190.2014.10.20",
   "RowKey":"18.17.3568687",
   "Timestamp":"2014-10-20T18:17:11.237+00:00",
   "ETag":"W/\\"   datetime'2014-10-20T18%3A17%3A11.237Z'\\""
}

众所周知，Azure Storage错误消息无济于事，并且无济于事，并且Googling对于因该特定错误而失败的批处理删除未返回任何信息.

Azure Storage error messages are notoriously and spectacularly unhelpful, and Googling has returned nothing about batch deletes failing with this particular error.

在使用本地开发存储和在生产环境中均失败.

This fails both when using local development storage and in production.

有什么想法吗?

推荐答案

意外的操作响应代码:0"基本上意味着该批处理中的第一个操作失败.失败的操作的索引将在引发的错误中返回，因此它使用户可以更轻松地更改失败的批处理中的特定操作.

'Unexpected Response Code for Operation: 0' basically means that the first operation in the batch failed. The index of the failed operation is returned in the error thrown so it makes it easier for users to go and change the specific operation in the batch that failed.

您可以通过捕获StorageException并检查以下内容来获取有关失败的请求和错误的更多信息:

You can get more information about the request that failed and the error by catching the StorageException and checking:

• exception.RequestInformation.HttpStatusCode
• exception.RequestInformation.ExtendedErrorInformation.ErrorCode
• exception.RequestInformation.ExtendedErrorInformation.ErrorMessage

• exception.RequestInformation.HttpStatusCode
• exception.RequestInformation.ExtendedErrorInformation.ErrorCode
• exception.RequestInformation.ExtendedErrorInformation.ErrorMessage

如果您使用OperationContext跟踪请求并使用OperationContext中合适的方法重载，则在OperationContext的最后结果中也可以使用相同的信息.

The same information is also available in the OperationContext's last result if you use an OperationContext to track the request and use suitable method overloads that take in the OperationContext.

我们将在以后考虑更改错误消息，以减少混乱.感谢您的反馈！

We will look at changing the error message in the future so it is less confusing. Thanks for the feedback!

这篇关于“意外的操作响应码:0"；执行Azure Table Storage批量删除时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！