Martin Schneppenheim

In what case it would be a breaking change? If I change the cron timer it won't update the existing repeating job, nor would it create a new one. Unless...

Actually I wonder how this would work, since after the edit of the cron timestamp it wouldn't add a second job with a different cron timer. I am not sure...

Are you looking for concurrent job processing? If so please see the full documentation and check Queue#process: https://github.com/OptimalBits/bull/blob/master/REFERENCE.md#queueprocess If you are really looking for a way to handle multiple jobs...

+1 For that feature, it should be very efficient though. Most likely one is adding and processing millions of jobs when using such an approach

You can also run ts-node directly with VSCode and therefore no transpilation is needed at all: ``` { "type": "node", "request": "launch", "name": "Request Worker", "runtimeArgs": [ "--nolazy", "-r", "${workspaceRoot}\\node_modules\\ts-node\\register"...

I agree with Bryan, if you make it optional and set the default to let's say "unnamed" you could still add additional pairs. We have ~20 tenants and we only...

We have one HA Pair (prometheus-1, prometheus-2) in each (kubernetes) cluster.

Right now yes, that's the issue all about I think. Just as Bryan said, there will be users like me who have exactly one Prometheus pair for each x-scope-orgid. We...

Adding this feature in the upstream Elasticsearch has been rejected. How can we proceed now?

I am not sure whether this is helpful at all because it's at such a high level, but I think the ECK operator could watch the ES data nodes and...