luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-nomad/dist/systemd/nomad.service

28 lines
678 B
SYSTEMD
Raw Normal View History

Basic configs and init scripts
2015-12-02 19:33:44 +00:00
[Unit]
Description=Nomad
Documentation=https://nomadproject.io/docs/
systemd unit - Wait for Network to be online This patch configures nomad to start only after the network is up and online. Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
2018-08-01 14:59:24 +00:00
Wants=network-online.target
After=network-online.target
Basic configs and init scripts
2015-12-02 19:33:44 +00:00
docs: sync systemd unit files; update deploy guide The systemd configs spread across our repo were fairly out of sync. This should get them on our best practices. The deployment guide also had some strange things like running Nomad as a non-root user. It would be fine for servers but completely breaks clients. For simplicity I simply removed the non-root user references.
2019-03-19 22:18:12 +00:00
# When using Nomad with Consul it is not necessary to start Consul first. These
# lines start Consul before Nomad as an optimization to avoid Nomad logging
# that Consul is unavailable at startup.
systemd unit - Do not restart if unit fails 3 times in 10s Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
2018-08-02 10:24:12 +00:00
#Wants=consul.service
#After=consul.service
Basic configs and init scripts
2015-12-02 19:33:44 +00:00
[Service]
docs: sync systemd unit files; update deploy guide The systemd configs spread across our repo were fairly out of sync. This should get them on our best practices. The deployment guide also had some strange things like running Nomad as a non-root user. It would be fine for servers but completely breaks clients. For simplicity I simply removed the non-root user references.
2019-03-19 22:18:12 +00:00
ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/local/bin/nomad agent -config /etc/nomad.d
set killmode/killsignal in systemd example The default (control-group) kill mode in systemd will kill the associated executors, leading to a commonly seen behavior of nomad client restarts losing all current allocations. setting the KillSignal to SIGINT seems to be a reasonable default, and allows things like leave_on_interrupt to function
2018-01-17 06:22:32 +00:00
KillMode=process
KillSignal=SIGINT
docs: sync systemd unit files; update deploy guide The systemd configs spread across our repo were fairly out of sync. This should get them on our best practices. The deployment guide also had some strange things like running Nomad as a non-root user. It would be fine for servers but completely breaks clients. For simplicity I simply removed the non-root user references.
2019-03-19 22:18:12 +00:00
LimitNOFILE=infinity
LimitNPROC=infinity
systemd unit - Restart on failure Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
2018-08-01 14:36:52 +00:00
Restart=on-failure
systemd unit - Do not restart if unit fails 3 times in 10s Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
2018-08-02 10:24:12 +00:00
RestartSec=2
StartLimitBurst=3
StartLimitIntervalSec=10
Remove the systemd process and threads limit systemd limits the number of process and threads you can create within the cgroup it creates for a given service. This is especially limiting if you have a high number of keys Nomad watches from Consul. Fixes #4649
2019-02-08 15:22:52 +00:00
TasksMax=infinity
nomad/examples: update systemd config files The existing nomad.service is having minor configuration and this change adds the following: * Install section that allows nomad to be able enabled in systemd * Default limit of open files is set to 65536
2016-03-30 07:26:26 +00:00
[Install]
WantedBy=multi-user.target