Open fafg opened 3 years ago
az servicebus queue create `
--resource-group <RG> `
--namespace-name <sb-namespace> `
--name <queue-name> `
--lock-duration "PT5M" `
--max-size 16384
using parameter --max-size the command blowup, without this parameter the command works. maybe using any other int parameter will break.
then you guys forces me to use arm template. =/
ok, using the standard tier i am limited to use up to 5gb, however using values different from these values --max-size on Standard sku namespace only supports upto [1024, 2048, 3072, 4096, 5120] GB
will show me that error =/
another problem. using these parameters:
--name $queueName `
--lock-duration "PT5M" `
--max-size 5120 `
--enable-duplicate-detection false `
--enable-session false `
--default-message-time-to-live "P90D" `
--enable-dead-lettering-on-message-expiration false `
--enable-batched-operations true `
--duplicate-detection-history-time-window "PT2M" `
--max-delivery-count 10 `
--status "Active" `
--enable-partitioning true `
--enable-express false
it generates a queue with this size:
80gb? but the messages previously said I can't create anything above 5gb since my tier is a standard one? 0.o
command line feedback:
{
"accessedAt": "0001-01-01T00:00:00",
"autoDeleteOnIdle": "10675199 days, 2:48:05.477581",
"countDetails": {
"activeMessageCount": 0,
"deadLetterMessageCount": 0,
"scheduledMessageCount": 0,
"transferDeadLetterMessageCount": 0,
"transferMessageCount": 0
},
"createdAt": "2021-02-19T19:07:33.113000+00:00",
"deadLetteringOnMessageExpiration": false,
"defaultMessageTimeToLive": "90 days, 0:00:00",
"duplicateDetectionHistoryTimeWindow": "0:02:00",
"enableBatchedOperations": true,
"enableExpress": false,
"enablePartitioning": true,
"forwardDeadLetteredMessagesTo": null,
"forwardTo": null,
"id": "wwwwwwwwww",
"location": "wwwwwww",
"lockDuration": "0:05:00",
"maxDeliveryCount": 10,
******* "maxSizeInMegabytes": 81920, *******
"messageCount": 0,
"name": "wwwwwwww",
"requiresDuplicateDetection": false,
"requiresSession": false,
"resourceGroup": "wwwwwwwww",
"sizeInBytes": 0,
"status": "Active",
"type": "Microsoft.ServiceBus/Namespaces/Queues",
"updatedAt": "2021-02-19T19:07:33.340000+00:00"
}
Guys, the issue i believe is regarding the value and the python explode.
but I could understand my issue.
I have started create the command line to deploy a queue, and then wisely I went to the portal had a look over a existent one in order to extract the properties from the arm template.
the generated arm template shows me the MAX-SIZE as 16gb, therefore i have used this value on the command line (it explode using this value). but talking with a friend, the partitioning enabled when you deploy with 1gb the portal shows 16gb. then when we have a max size of 5gb and partition enabled we get 80gb as expected.
so, the issue then is the command that is exploding with values above 5gb and not showing a properly feedback message.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jfggdl, @axisc.
Author: | fafg |
---|---|
Assignees: | - |
Labels: | `Error Handling`, `Service Attention`, `Service Bus`, `needs-triage`, `question` |
Milestone: | - |
route to appropriate team
@fafg- Thank you for bringing this to our attention. You're right about the total size to be addition of all partitions involved, I would work within the team to have an informative error message. I would keep you posted for additional updates.
{ "error": { "code": "OK", "message": "OK CorrelationId: ed2a6c29-0046-4145-9162-b012eeccba0f" }, "id": null, "name": null, "rights": null, "type": null }
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az servicebus queue create
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az servicebus queue create --resource-group {} --namespace-name {} --name {} --lock-duration {} --max-size {} --enable-duplicate-detection {} --enable-session {} --default-message-time-to-live {} --enable-dead-lettering-on-message-expiration {} --enable-batched-operations {} --duplicate-detection-history-time-window {} --max-delivery-count {} --status {} --auto-delete-on-idle {} --enable-partitioning {} --enable-express {}
Expected Behavior
Environment Summary
Additional Context