Follower only River job processors

[allancalix]

Hello!

I'm doing a kind of hacky thing and using a silo'd river queue as a make-shift container scheduler for batch jobs. The setup is the default queue runs the normal jobs for my application but tasks which require special system dependencies get dispatched to a split queue and picked up by the specialized nodes.

So far it works well and has the nice property of being able to kick off containers from your application just by creating jobs like normal.

One awkward part is leader election. Periodic job configurations have to sprawl to these other binaries that are pretty sparse (mostly just simple control plane code and startup) because they may get elected leader and if the periodic jobs aren't there it causes the entire system not to register the jobs.

Curious if anyone has done anything like this. What I found myself wanting was a way to turn off the ability for a client to participate in leader election at all - they act solely as followers and consumers of jobs on the queue.

Anyway cheers!

[brandur]

Giving clients an option to elect not to participate in leader electionship doesn't strike me as the worse thing ever. @bgentry Thoughts?