Clustering in quartz can be handled by having individual schedule instances point to the same job store, which essentially synchronizes their activity based on database state. Here's a bit of background on that:
The timer configuration for your binding can be set using a quartz.properties file included in the root of your deployment. The timer name for the quartz binding needs to match the schedule name in your quartz configuration.
If the above doesn't meet your requirements then you are likely looking at setting up your own singleton instance for the cluster to coordinate the timer.
Nice, but I have only NoSQL DB in my setup
May be I should find some lightweight distributed DB for storing such info, do you know one? H2 is a candidate, but if I only setup it in standalone mode + clustered.