From de6edeedccf041e005db9eac959164f64f4e26ee Mon Sep 17 00:00:00 2001
From: sirkrypt0 <22522058+sirkrypt0@users.noreply.github.com>
Date: Thu, 29 Jul 2021 14:01:31 +0200
Subject: [PATCH] Add docs on how to avoid Nomad rate limiting

Without this configuration, Nomad caps the maximum concurrent connections
of a unique client to 100. This is not sufficient for our use case.
---
 docs/configuration.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/docs/configuration.md b/docs/configuration.md
index 991f760..3c162d5 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -16,4 +16,16 @@ As a subsystem of Poseidon, Nomad can and should also be configured accordingly.
 ### Scheduler
 
 By default, Nomad uses a bin-packing scheduler. This places all Jobs on one host. In our case, a high load then leads to one Nomad client being fully utilised while the others remain mostly idle.
-To mitigate the overload of a Nomad client, the ["spread" scheduler algorithm](https://www.nomadproject.io/api-docs/operator/scheduler#update-scheduler-configuration) should be used.
\ No newline at end of file
+To mitigate the overload of a Nomad client, the ["spread" scheduler algorithm](https://www.nomadproject.io/api-docs/operator/scheduler#update-scheduler-configuration) should be used.
+
+### Maximum Connections per Client
+
+By default, Nomad only allows 100 maximum concurrent connections per client. However, as Poseidon is a client, this would significantly impair and limit the performance of Poseidon. Thus, this limit should be disabled.
+
+To do so, ensure the following configuration is set in your Nomad agents, for example by adding it to `/etc/nomad.d/base.hcl`:
+
+```hcl
+limits {
+    http_max_conns_per_client = 0
+}
+```