Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
Consul v1.17.0
Revision 4e3f428b
Build Date 2023-11-03T14:56:56Z
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
Vault
Vault v1.15.2 (cf1b5cafa047bc8e4a3f93444fcb4011593b92cb), built 2023-11-06T11:33:28Z
Issue
I have a job RocketChat
Rocketchat needs mongoDB
I use Consul service mesh to connect Rocket to its database mongoDB
But after few hours, I need to restart job because RocketChat is unusable , very very slow, messages cannot be sent etc.
I insert a dirty cron command to restart job every day at 5:00 am. It's been working like this for a year.
Two weeks ago, I decided to stop using Consul service mesh and rework job with Consul DNS resolution only. And! It works! And since 13 days, I don't need to restart job. π₯³
I don't know how to explain this.
Now It works without Consul service mesh, it's good, but, I feel disturbate to not use Consul service mesh.
Am I forgetting something?
This is my previous version of job, with Consul service mesh:
Hello @fred-gb! Looking at your issue, the most likely culprit is Envoy Proxy configuration error, not Nomad in this case. I would recommend you to take a look at it. You can find some guidance on what to look for here and here. I hope this helps you.
Bonjour ππ»
Nomad version
Operating system and Environment details
Consul
Vault
Issue
I have a job RocketChat Rocketchat needs mongoDB I use Consul service mesh to connect Rocket to its database mongoDB But after few hours, I need to restart job because RocketChat is unusable , very very slow, messages cannot be sent etc.
I insert a dirty cron command to restart job every day at 5:00 am. It's been working like this for a year.
Two weeks ago, I decided to stop using Consul service mesh and rework job with Consul DNS resolution only. And! It works! And since 13 days, I don't need to restart job. π₯³
I don't know how to explain this.
Now It works without Consul service mesh, it's good, but, I feel disturbate to not use Consul service mesh.
Am I forgetting something?
This is my previous version of job, with Consul service mesh:
And version without Consul service mesh, only Consul DNS resolution:
Thanks