AFAIK quartz work is always performed on a single node, which is selected by Quartz. Annotating @NonConcurrent only prevents Quartz from doing the same job on a specific node.
In other words, you cannot force Quartz to do the job on multiple nodes at the same time. He always selects one node for the job.
To understand what you described, you may need several tasks (using the same class of tasks and without associated triggers). Then you will need to perform some kind of orchestra task, which will be remotely connected, for example. via JMX or RMI, to individual nodes and run tasks manually.
You can check our QuartzDesk product ( www.quartzdesk.com ), which provides a web service that provides a single endpoint through which you can connect to individual instances of the Quartz scheduler and, for example, run tasks on them.
source share