Details
-
Feature Request
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
-
None
Description
Created on behalf of
User Story (Required on creation):
Single database for multiple tenants, but split the workload of asynchronous jobs across separate engine instances.
The reasoning is that we have some fairly large differences in loads as produced by our tenants, and in some cases, one tenant would affect throughput of another.
By adding parameters to the job executor, to tell it for which tenants to process jobs.
Functional Requirements (Required before implementation):
- The Job Executor can process jobs per tenant
- A configuration property/ies exist that define jobs of which tenants should be (not) processed.