Azure队列主体太大，超过了最大允许限制 [英] Azure Queue body is too large and exceeds the maximum permissible limit

问题描述

当将消息从我的c ++应用程序推送到Azure存储时，我的存储队列出现以下错误(不是BLOB-我知道其他人已经看到了blob):

I am getting the following error with my storage queue (NOT BLOB - I know others have seen this with the blob) when pushing the message from my c++ app to Azure Storage:

请求正文太大，超过了最大允许限制.

The request body is too large and exceeds the maximum permissible limit.

我知道我可能需要削减json，但是还有其他建议吗? (如增加某处的消息大小?)

I'm aware that I probably need to cut the json down, but are there any other suggestions? (as in increase message size somewhere?)

推荐答案

正如其他人所述，Azure存储队列消息大小限制(64K)是一个硬限制.

As others have stated, the Azure Storage Queue message size limit (64K) is a hard limit.

除了编码，压缩(最小化)等以外，解决此限制的最常见模式是不将有效负载存储在队列消息中；而是将其存储在Blob存储之类的文件中，并且仅存储消息类型&元数据(如果需要)，以及指向包含要处理的有效载荷的blob的URI.

Aside from encoding, compression (minification), etc: The most common pattern to work around this limit is to not store your payload in the queue message; rather, store it in something like Blob storage, and only store the message type & metadata (if needed), along with a URI pointing to the blob containing your payload to process.

通过遵循此模式，并为您的有效负载使用Blob存储，您实际上可以将潜在的有效负载大小设置为4 TB以上.而且，如果需要，您还可以保留有效负载(而队列消息将在处理后被删除).

By following this pattern, and using blob storage for your payload, you effectively have potential payload size of 4+ TB. And you also have the ability to persist your payload if needed (whereas queue messages are deleted after processing).

这篇关于Azure队列主体太大，超过了最大允许限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！