Same Azure Cosmos DB one time it runs other time shows message Size is too large
I am writing Azure Cosmos DB stored procedure in azure portal , I am checking the what is max size response it can give initially it gave me 4.8 MB response later on any size more that it was showing error of message size is too large . Later on after 5 min executed same procedure and same parameters it was showing error of too large page size.
// SAMPLE STORED PROCEDURE
function sample(prefix)
var collection = getContext().getCollection();
// Query documents and take 1st item.
var isAccepted = collection.queryDocuments(
collection.getSelfLink(),
'SELECT r.data.truckSerialNo FROM root r',pageSize : -1,
function (err, feed, options)
if (err) throw err;
// Check the feed and if empty, set the body to 'no docs found',
// else take 1st element from feed
if (!feed );
if (!isAccepted) throw new Error('The query was not accepted by the server.');
and error
Failed to execute stored procedure testProcedure for collection
iotcollection:
"code":400,"body":""code":"BadRequest","message":"Message:
\"Errors\":[\"Encountered exception while executing function.
Exception = Error: Resulting message would be too large because of
\\"Body\\". Return from script with current message and use
continuation token to call the script again or modify your
script.\r\nStack trace: Error: Resulting message would be too
large because of \\"Body\\". Return from script with current
message and use continuation token to call the script again or modify
your script.\n at validateSize (bulkUpsert_v_1_0.js:177:25)\n
at setValueInternal (bulkUpsert\"]rnActivityId:
d61226ab-4d5e-4a3d-aa09-83351649ce4c, Request URI:
/apps/59d3b9ef-17ca-4bbf-8a11-39d0199a8d29/services/1b26e00f-1f51-4d34-88ec-4090b8e7db00/partitions/45a313b7-2cf2-419e-9885-48bf9cfe6277/replicas/131862936473830809p/,
RequestStats: rnRequestStartTime: 2018-11-10T06:41:26.3320532Z,
Number of regions attempted: 1rn, SDK:
Microsoft.Azure.Documents.Common/2.1.0.0"","activityId":"d61226ab-4d5e-4a3d-aa09-83351649ce4c","substatus":413
azure-cosmosdb azure-cosmosdb-sqlapi edited Nov 12 '18 at 7:56
Jay Gong
7,9461512
asked Nov 10 '18 at 7:30
Amjath Khan
488
add a comment |
I am writing Azure Cosmos DB stored procedure in azure portal , I am checking the what is max size response it can give initially it gave me 4.8 MB response later on any size more that it was showing error of message size is too large . Later on after 5 min executed same procedure and same parameters it was showing error of too large page size.
// SAMPLE STORED PROCEDURE
function sample(prefix)
var collection = getContext().getCollection();
// Query documents and take 1st item.
var isAccepted = collection.queryDocuments(
collection.getSelfLink(),
'SELECT r.data.truckSerialNo FROM root r',pageSize : -1,
function (err, feed, options)
if (err) throw err;
// Check the feed and if empty, set the body to 'no docs found',
// else take 1st element from feed
if (!feed );
if (!isAccepted) throw new Error('The query was not accepted by the server.');
and error
Failed to execute stored procedure testProcedure for collection
iotcollection:
"code":400,"body":""code":"BadRequest","message":"Message:
\"Errors\":[\"Encountered exception while executing function.
Exception = Error: Resulting message would be too large because of
\\"Body\\". Return from script with current message and use
continuation token to call the script again or modify your
script.\r\nStack trace: Error: Resulting message would be too
large because of \\"Body\\". Return from script with current
message and use continuation token to call the script again or modify
your script.\n at validateSize (bulkUpsert_v_1_0.js:177:25)\n
at setValueInternal (bulkUpsert\"]rnActivityId:
d61226ab-4d5e-4a3d-aa09-83351649ce4c, Request URI:
/apps/59d3b9ef-17ca-4bbf-8a11-39d0199a8d29/services/1b26e00f-1f51-4d34-88ec-4090b8e7db00/partitions/45a313b7-2cf2-419e-9885-48bf9cfe6277/replicas/131862936473830809p/,
RequestStats: rnRequestStartTime: 2018-11-10T06:41:26.3320532Z,
Number of regions attempted: 1rn, SDK:
Microsoft.Azure.Documents.Common/2.1.0.0"","activityId":"d61226ab-4d5e-4a3d-aa09-83351649ce4c","substatus":413
azure-cosmosdb azure-cosmosdb-sqlapi edited Nov 12 '18 at 7:56
Jay Gong
7,9461512
asked Nov 10 '18 at 7:30
Amjath Khan
488
Possible duplicate of Cosmos DB out of Memory exception while executing stored procedure
– Josh
Nov 11 '18 at 23:18
Please refrain from asking the same question more than once with tweaks to the verbiage. This is the third time you’ve pasted the same code and asked about oversized responses.
– Josh
Nov 11 '18 at 23:21
Hi,Amjath,does my answer helps you?
– Jay Gong
Dec 3 '18 at 5:54
add a comment |
I am writing Azure Cosmos DB stored procedure in azure portal , I am checking the what is max size response it can give initially it gave me 4.8 MB response later on any size more that it was showing error of message size is too large . Later on after 5 min executed same procedure and same parameters it was showing error of too large page size.
// SAMPLE STORED PROCEDURE
function sample(prefix)
var collection = getContext().getCollection();
// Query documents and take 1st item.
var isAccepted = collection.queryDocuments(
collection.getSelfLink(),
'SELECT r.data.truckSerialNo FROM root r',pageSize : -1,
function (err, feed, options)
if (err) throw err;
// Check the feed and if empty, set the body to 'no docs found',
// else take 1st element from feed
if (!feed );
if (!isAccepted) throw new Error('The query was not accepted by the server.');
and error
Failed to execute stored procedure testProcedure for collection
iotcollection:
"code":400,"body":""code":"BadRequest","message":"Message:
\"Errors\":[\"Encountered exception while executing function.
Exception = Error: Resulting message would be too large because of
\\"Body\\". Return from script with current message and use
continuation token to call the script again or modify your
script.\r\nStack trace: Error: Resulting message would be too
large because of \\"Body\\". Return from script with current
message and use continuation token to call the script again or modify
your script.\n at validateSize (bulkUpsert_v_1_0.js:177:25)\n
at setValueInternal (bulkUpsert\"]rnActivityId:
d61226ab-4d5e-4a3d-aa09-83351649ce4c, Request URI:
/apps/59d3b9ef-17ca-4bbf-8a11-39d0199a8d29/services/1b26e00f-1f51-4d34-88ec-4090b8e7db00/partitions/45a313b7-2cf2-419e-9885-48bf9cfe6277/replicas/131862936473830809p/,
RequestStats: rnRequestStartTime: 2018-11-10T06:41:26.3320532Z,
Number of regions attempted: 1rn, SDK:
Microsoft.Azure.Documents.Common/2.1.0.0"","activityId":"d61226ab-4d5e-4a3d-aa09-83351649ce4c","substatus":413
azure-cosmosdb azure-cosmosdb-sqlapi edited Nov 12 '18 at 7:56
Jay Gong
7,9461512
asked Nov 10 '18 at 7:30
Amjath Khan
488
I am writing Azure Cosmos DB stored procedure in azure portal , I am checking the what is max size response it can give initially it gave me 4.8 MB response later on any size more that it was showing error of message size is too large . Later on after 5 min executed same procedure and same parameters it was showing error of too large page size.
// SAMPLE STORED PROCEDURE
function sample(prefix)
var collection = getContext().getCollection();
// Query documents and take 1st item.
var isAccepted = collection.queryDocuments(
collection.getSelfLink(),
'SELECT r.data.truckSerialNo FROM root r',pageSize : -1,
function (err, feed, options)
if (err) throw err;
// Check the feed and if empty, set the body to 'no docs found',
// else take 1st element from feed
if (!feed );
if (!isAccepted) throw new Error('The query was not accepted by the server.');
and error
Failed to execute stored procedure testProcedure for collection
iotcollection:
"code":400,"body":""code":"BadRequest","message":"Message:
\"Errors\":[\"Encountered exception while executing function.
Exception = Error: Resulting message would be too large because of
\\"Body\\". Return from script with current message and use
continuation token to call the script again or modify your
script.\r\nStack trace: Error: Resulting message would be too
large because of \\"Body\\". Return from script with current
message and use continuation token to call the script again or modify
your script.\n at validateSize (bulkUpsert_v_1_0.js:177:25)\n
at setValueInternal (bulkUpsert\"]rnActivityId:
d61226ab-4d5e-4a3d-aa09-83351649ce4c, Request URI:
/apps/59d3b9ef-17ca-4bbf-8a11-39d0199a8d29/services/1b26e00f-1f51-4d34-88ec-4090b8e7db00/partitions/45a313b7-2cf2-419e-9885-48bf9cfe6277/replicas/131862936473830809p/,
RequestStats: rnRequestStartTime: 2018-11-10T06:41:26.3320532Z,
Number of regions attempted: 1rn, SDK:
Microsoft.Azure.Documents.Common/2.1.0.0"","activityId":"d61226ab-4d5e-4a3d-aa09-83351649ce4c","substatus":413
azure-cosmosdb azure-cosmosdb-sqlapi azure-cosmosdb azure-cosmosdb-sqlapi edited Nov 12 '18 at 7:56
Jay Gong
7,9461512
asked Nov 10 '18 at 7:30
Amjath Khan
488
edited Nov 12 '18 at 7:56
Jay Gong
7,9461512
asked Nov 10 '18 at 7:30
Amjath Khan
488
edited Nov 12 '18 at 7:56
Jay Gong
7,9461512
edited Nov 12 '18 at 7:56
Jay Gong
7,9461512
edited Nov 12 '18 at 7:56
Jay Gong
7,9461512
7,9461512
asked Nov 10 '18 at 7:30
Amjath Khan
488
asked Nov 10 '18 at 7:30
Amjath Khan
488
asked Nov 10 '18 at 7:30
Amjath Khan
488
488
Possible duplicate of Cosmos DB out of Memory exception while executing stored procedure
– Josh
Nov 11 '18 at 23:18
Please refrain from asking the same question more than once with tweaks to the verbiage. This is the third time you’ve pasted the same code and asked about oversized responses.
– Josh
Nov 11 '18 at 23:21
Hi,Amjath,does my answer helps you?
– Jay Gong
Dec 3 '18 at 5:54
add a comment |
Possible duplicate of Cosmos DB out of Memory exception while executing stored procedure
– Josh
Nov 11 '18 at 23:18
Please refrain from asking the same question more than once with tweaks to the verbiage. This is the third time you’ve pasted the same code and asked about oversized responses.
– Josh
Nov 11 '18 at 23:21
Hi,Amjath,does my answer helps you?
– Jay Gong
Dec 3 '18 at 5:54
Possible duplicate of Cosmos DB out of Memory exception while executing stored procedure
– Josh
Nov 11 '18 at 23:18
Possible duplicate of Cosmos DB out of Memory exception while executing stored procedure
– Josh
Nov 11 '18 at 23:18
Please refrain from asking the same question more than once with tweaks to the verbiage. This is the third time you’ve pasted the same code and asked about oversized responses.
– Josh
Nov 11 '18 at 23:21
Please refrain from asking the same question more than once with tweaks to the verbiage. This is the third time you’ve pasted the same code and asked about oversized responses.
– Josh
Nov 11 '18 at 23:21
Hi,Amjath,does my answer helps you?
– Jay Gong
Dec 3 '18 at 5:54
Hi,Amjath,does my answer helps you?
– Jay Gong
Dec 3 '18 at 5:54
add a comment |
1 Answer
1
active
oldest
votes
Per my experience, pageSize : -1 setting is not recommanded strongly when your data is too huge in cosmos db query operation. Continuation token(namely x-ms-continuation-token in cosmos db rest api) need to be considered into your business. Please refer to my previous case:CosmosDB stored procedure not returning all documents.
As you said, later on after 5 min executed same procedure and same parameters it was showing error of too large page size. The size limit is total response which including other Response Headers,not only the body part. In addition, the query operation returns maximum results based on current performance if you set pageSize : -1. It's not fixed.
answered Nov 12 '18 at 8:10
Jay Gong
7,9461512
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236915%2fsame-azure-cosmos-db-one-time-it-runs-other-time-shows-message-size-is-too-large%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Per my experience, pageSize : -1 setting is not recommanded strongly when your data is too huge in cosmos db query operation. Continuation token(namely x-ms-continuation-token in cosmos db rest api) need to be considered into your business. Please refer to my previous case:CosmosDB stored procedure not returning all documents.
As you said, later on after 5 min executed same procedure and same parameters it was showing error of too large page size. The size limit is total response which including other Response Headers,not only the body part. In addition, the query operation returns maximum results based on current performance if you set pageSize : -1. It's not fixed.
answered Nov 12 '18 at 8:10
Jay Gong
7,9461512
add a comment |
Per my experience, pageSize : -1 setting is not recommanded strongly when your data is too huge in cosmos db query operation. Continuation token(namely x-ms-continuation-token in cosmos db rest api) need to be considered into your business. Please refer to my previous case:CosmosDB stored procedure not returning all documents.
As you said, later on after 5 min executed same procedure and same parameters it was showing error of too large page size. The size limit is total response which including other Response Headers,not only the body part. In addition, the query operation returns maximum results based on current performance if you set pageSize : -1. It's not fixed.
answered Nov 12 '18 at 8:10
Jay Gong
7,9461512
add a comment |
Per my experience, pageSize : -1 setting is not recommanded strongly when your data is too huge in cosmos db query operation. Continuation token(namely x-ms-continuation-token in cosmos db rest api) need to be considered into your business. Please refer to my previous case:CosmosDB stored procedure not returning all documents.
As you said, later on after 5 min executed same procedure and same parameters it was showing error of too large page size. The size limit is total response which including other Response Headers,not only the body part. In addition, the query operation returns maximum results based on current performance if you set pageSize : -1. It's not fixed.
answered Nov 12 '18 at 8:10
Jay Gong
7,9461512
Per my experience, pageSize : -1 setting is not recommanded strongly when your data is too huge in cosmos db query operation. Continuation token(namely x-ms-continuation-token in cosmos db rest api) need to be considered into your business. Please refer to my previous case:CosmosDB stored procedure not returning all documents.
As you said, later on after 5 min executed same procedure and same parameters it was showing error of too large page size. The size limit is total response which including other Response Headers,not only the body part. In addition, the query operation returns maximum results based on current performance if you set pageSize : -1. It's not fixed.
answered Nov 12 '18 at 8:10
Jay Gong
7,9461512
answered Nov 12 '18 at 8:10
Jay Gong
7,9461512
answered Nov 12 '18 at 8:10
Jay Gong
7,9461512
answered Nov 12 '18 at 8:10
Jay Gong
7,9461512
7,9461512
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236915%2fsame-azure-cosmos-db-one-time-it-runs-other-time-shows-message-size-is-too-large%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Possible duplicate of Cosmos DB out of Memory exception while executing stored procedure
– Josh
Nov 11 '18 at 23:18
Please refrain from asking the same question more than once with tweaks to the verbiage. This is the third time you’ve pasted the same code and asked about oversized responses.
– Josh
Nov 11 '18 at 23:21
Hi,Amjath,does my answer helps you?
– Jay Gong
Dec 3 '18 at 5:54