Michael Schurter

To ease the configuration headache, perhaps you could only expose this functionality through the explicit topic/channel creation endpoints? So the _default_ for all channels would be the global `mem-queue-size`, but...

@mreiferson Perhaps v1 could leave configuration consistency up to users? That's already the case with `mem-queue-size`, different peers in a cluster could be configured differently and `nsqd` won't try to...

Sorry for the delay and frustration @wurosh and thanks for the contribution! There's a gRPC layer between the driver and executor which needs the WorkDir plumbed through. To make matters...

Ha, don't feel bad. Nothing in our docs or tooling help you with this, and I'm not sure how to fix that. It's a really unfortunate dev story, and a...

Good timing! I'm working on the GC as we speak and the logging will be improved. `forced collection` is the reason. Did you force a GC via the `/v1/system/gc` HTTP...

#3445 includes some logging improvements to the GC but does not directly address the items you list.

Hi @holtwilkins, Nomad servers periodically GC dead jobs and force GC their allocations on their client nodes. You can configure that interval on servers with the [`job_gc_threshold`](https://www.nomadproject.io/docs/agent/configuration/server.html#job_gc_threshold) parameter. It defaults...

That's super exciting @calavera! nomadproject.io itself uses Netlify, so it would be exciting to be "self-hosted" in a way. Unfortunately this feature is not planned for the upcoming 0.11.x or...

Unfortunately no updates. Sorry for letting this slip. Definitely still something we want to do, but I don't want to keep overpromising and underdelivering on timelines. :grimacing:

Converted to draft to inspect CI failure.