You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is for tracking outcomes and recommendations we can provide to help Cloud Dedicated customers scale or adjust their write workloads to fit their cluster.
Regarding Cloud Dedicated write limits...
After some digging, my understanding, which seems to be inline with the customer's request, is that
Dedicated doesn't currently return 429. In the same context
503 means Ingesters aren't available to handle the data.
There is ongoing work to address scaling and limiting of writes
No "cluster-sized" limits or recommendations are provided to customers.
We can eventually incorporate the outcome/findings/guidance from that work to explain how writes and Ingestors are scaled and to make recommendations in the docs.
For now, I'm not sure we can say anything beyond "Try the request again."
The text was updated successfully, but these errors were encountered:
This issue is for tracking outcomes and recommendations we can provide to help Cloud Dedicated customers scale or adjust their write workloads to fit their cluster.
Regarding Cloud Dedicated write limits...
After some digging, my understanding, which seems to be inline with the customer's request, is that
429
. In the same context503
means Ingesters aren't available to handle the data.We can eventually incorporate the outcome/findings/guidance from that work to explain how writes and Ingestors are scaled and to make recommendations in the docs.
For now, I'm not sure we can say anything beyond "Try the request again."
The text was updated successfully, but these errors were encountered: