htwkmooc/poseidon
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add docs on how to avoid Nomad rate limiting

Browse Source 
Without this configuration, Nomad caps the maximum concurrent connections
of a unique client to 100. This is not sufficient for our use case.
This commit is contained in:
sirkrypt0
2021-07-29 14:01:31 +02:00
committed by Jan-Eric Hellenberg
parent f03d07cd54
commit de6edeedcc
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/configuration.md
View File

@ -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.
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
}
```