Open follis opened 5 years ago
Linking to #13158 which is maybe one piece of this epic.
The following could be another piece.
Not very severe, but in our environment we have 2 (or more) completely independent servers. Batch processes are run only on one of them since the user request to start batch is received by only one (chosen randomly by load balancer). The servers currently don't know anything about each other, technically spoken. Would be great if they could divide threads (partitions) on each other in a cloud environment.
@nicolas-tg-ch - Though we don't have any more updates of this plan to report currently, we have discussed similar ideas (scaling partitions across multiple container instances in Kubernetes internally). Thank you for mentioning your interest in this kind of function.
The existing JSR-352 support has some issues running in a dynamically provisioned cloud environment. We need to determine how batch should behave in this environment and what changes are required to make that happen.