Go to file
Will Jordan 5354409b1a
Return 429 response on HTTP max connection limit (#13621)
Return 429 response on HTTP max connection limit. Instead of silently closing
the connection, return a `429 Too Many Requests` HTTP response with a helpful
error message to aid debugging when the connection limit is unintentionally
reached.

Set a 10-millisecond write timeout and rate limiter for connection-limit 429
response to prevent writing the HTTP response from consuming too many server
resources.

Add `nomad.agent.http.exceeded metric` counting the number of HTTP connections
exceeding concurrency limit.
2022-07-20 14:12:21 -04:00
.changelog Return 429 response on HTTP max connection limit (#13621) 2022-07-20 14:12:21 -04:00
.circleci
.github
.release packaging: restart nomad service after package update (#13773) 2022-07-15 14:20:04 -07:00
.semgrep Add semgrep rule to catch non-determinism in FSM (#13725) 2022-07-12 15:44:24 -07:00
.tours
acl
api chore(deps): bump github.com/mitchellh/mapstructure from 1.4.3 to 1.5.0 in /api (#12725) 2022-07-13 11:57:16 -07:00
ci
client
command Return 429 response on HTTP max connection limit (#13621) 2022-07-20 14:12:21 -04:00
contributing
demo
dev
drivers
e2e e2e: add nsd simple load balancing test 2022-07-14 15:07:19 -05:00
helper tests: add a space between node name and timestamp (#13750) 2022-07-13 16:23:03 -04:00
integrations
internal/testing/apitests
jobspec
jobspec2
lib
nomad cleanup: tweaks from cr feedback 2022-07-20 10:42:35 -05:00
plugins
scheduler
scripts
terraform
testutil
tools
ui Add a title to the evals route (#13865) 2022-07-20 13:28:06 -04:00
version Prepare for next release 2022-07-13 19:34:32 -04:00
website Return 429 response on HTTP max connection limit (#13621) 2022-07-20 14:12:21 -04:00
.git-blame-ignore-revs
.gitattributes
.gitignore
.go-version
.golangci.yml
.semgrepignore
CHANGELOG.md Merge release 1.3.2 files 2022-07-13 19:35:54 -04:00
CODEOWNERS
GNUmakefile Prepare for next release 2022-07-13 19:34:32 -04:00
LICENSE
README.md
Vagrantfile
build_linux_arm.go
go.mod cleanup: example refactoring out map[string]struct{} using set.Set 2022-07-19 22:50:49 -05:00
go.sum cleanup: example refactoring out map[string]struct{} using set.Set 2022-07-19 22:50:49 -05:00
main.go
main_test.go

README.md

Nomad Build Status Discuss

HashiCorp Nomad logo

Nomad is a simple and flexible workload orchestrator to deploy and manage containers (docker, podman), non-containerized applications (executable, Java), and virtual machines (qemu) across on-prem and clouds at scale.

Nomad is supported on Linux, Windows, and macOS. A commercial version of Nomad, Nomad Enterprise, is also available.

Nomad provides several key features:

  • Deploy Containers and Legacy Applications: Nomads flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable task drivers.

  • Simple & Reliable: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.

  • Device Plugins & GPU Support: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses device plugins to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.

  • Federation for Multi-Region, Multi-Cloud: Nomad was designed to support infrastructure at a global scale. Nomad supports federation out-of-the-box and can deploy applications across multiple regions and clouds.

  • Proven Scalability: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.

  • HashiCorp Ecosystem: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.

Quick Start

Testing

See Learn: Getting Started for instructions on setting up a local Nomad cluster for non-production use.

Optionally, find Terraform manifests for bringing up a development Nomad cluster on a public cloud in the terraform directory.

Production

See Learn: Nomad Reference Architecture for recommended practices and a reference architecture for production deployments.

Documentation

Full, comprehensive documentation is available on the Nomad website: https://www.nomadproject.io/docs

Guides are available on HashiCorp Learn.

Contributing

See the contributing directory for more developer documentation.