Multiple Instances or Live Reload

[jpdsteno]

Currently I have some bree jobs that run on a cron schedule and cannot overlap or run concurrently. To solve this, we use an exclusive lock during app startup so that only a single instance of bree runs in HA mode. We also have other jobs that follow the competing consumer pattern, and should run concurrently.

Ideally, I'd like bree to live update when a new job is added via the api, but that does not seem to work unless bree is stopped and restarted. As a work around, I create two discrete bree instances, one for exclusive jobs and one for concurrent jobs. My question is, is creating multiple bree instances safe, and is there a way to live reload without stopping other jobs?

[shadowgate15]

You can always use bree.start with the job name passed as the argument to start the job with scheduling setup. You would need to define "safe" for me to answer you other question. The operation of bree itself, i.e. scheduling jobs, would not conflict with each other. That doesn't say anything about what the jobs actually do though.

[jpdsteno]

That sounds great, thanks! I meant "safe" as in, bree does not rely on static or shared data that could lead to consistency issues should multiple instances run within the same process.