Ability to Set Automatic Allocation Refreshment (Allocation Lifecycle)

[habibimustafa]

It would be nice if Nomad could implement an allocation lifecycle feature that automatically refreshes allocations after a specified number of days. Instead of having allocations run indefinitely, Nomad could replace an old allocation with a new one, keeping services fresh and avoiding issues associated with long-running allocations.

Use Cases

I have faced several issues from long-running allocations (specially on docker) such as memory leaks, stale connections, disks full of stale logs, or other surprising obstacles.

Attempted Solutions

• Manual Restarts:
  Currently, I have to manually restart allocations or trigger redeployments. This method is error-prone and can lead to downtime if not managed carefully.

• External Scheduling Tools:
  Creating cron jobs or custom scripts and run it under Nomad batch job to force allocation refreshes, but these solutions are clunky and lack tight integration with Nomad’s native scheduling and resource management. This approach is also less efficient for large allocations.

[jrasell]

Hi @habibimustafa and thanks for raising this issue. It is certainly an interesting idea to have something similar to this within Nomad, most likely the Nomad client. While I don't believe this is something we will be able to prioritise quickly, I'll add it to our backlog for further discussion.

[habibimustafa]

Its OK @jrasell
Thank you