Spaces:
Running
Running
Download backend/docs/docs-cloud-reference-limitations.txt from tomeese/support-ticket-analyzer: direct link, hf CLI and curl.
- Browser
- Download file 2.26 kB
-
https://huggingface.co/spaces/tomeese/support-ticket-analyzer/resolve/main/backend/docs/docs-cloud-reference-limitations.txt
- Command line
-
hf download hf://spaces/tomeese/support-ticket-analyzer/backend/docs/docs-cloud-reference-limitations.txt
-
curl -L -o docs-cloud-reference-limitations.txt https://huggingface.co/spaces/tomeese/support-ticket-analyzer/resolve/main/backend/docs/docs-cloud-reference-limitations.txt
2.26 kB
| TITLE: Halyard Cloud limitations | |
| URL: | |
| ============================================================ | |
| Halyard Cloud limitations | |
| This page describes the limitations in Halyard Cloud. Limitations are organized by category and include workarounds where available. | |
| Limited regions and instance types : May not have optimal placement Workaround : Request additional regions via support Status : Ongoing expansion | |
| Workaround : Request additional regions via support | |
| Status : Ongoing expansion | |
| Bring your own account (BYOA) is not available : Halyard-managed AWS accounts only Workaround : Use VPC peering for connectivity to your infrastructure | |
| Workaround : Use VPC peering for connectivity to your infrastructure | |
| Single cloud provider : AWS only Timeline : Multi-cloud support planned for 2026 | |
| Timeline : Multi-cloud support planned for 2026 | |
| The following limits are enforced to ensure stability and optimal performance: | |
| Rule | |
| Reason | |
| Example | |
| Cluster size ÷ zone count = whole number | |
| Even distribution across zones | |
| 6 nodes ÷ 3 zones = 2 nodes/zone ✅ | |
| Cluster size ÷ replication factor = whole number | |
| Balanced replication | |
| 9 nodes ÷ 3 replicas = 3 sets ✅ | |
| Max 15 nodes default | |
| Resource management | |
| Contact support for higher limits | |
| Single namespace per cluster - Each Halyard Cloud cluster supports only one namespace. To isolate workloads or data, use sets or provision separate clusters for complete isolation. | |
| After their initial configuration, the following settings cannot be changed: | |
| Replication factor - Plan carefully for your durability needs | |
| Zone count - Consider growth when selecting zones | |
| Strong consistency + Memory storage - Choose one consistency model | |
| Not all Halyard server settings are available through the cloud - See advanced config for more information | |
| Check workarounds in the tables above | |
| Review best practices for optimal configurations | |
| Contact support for limit increases or timeline questions | |
| Join community for peer discussions and updates | |
| Technical limits : Contact your technical account manager | |
| Billing limits : Discuss with your sales engineer | |
| Timeline questions : We plan to publish a public roadmap for 2026 features | |
| Cluster planning best practices | |
| API usage patterns | |
| Monitoring and alerting |