Quartz plugin issues

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Quartz plugin issues

Luis Muniz-2
Hi,

I am deploying my grails application to a cluster and thus have to clusterize my quartz jobs.

However, some jobs mustn't be clusterized, some jobs need to be local to the node where they are aexecuted, and must run regardless of other jobs of teh same type being run on other nodes.
Apparently the grails quartz plugin uses version 1.7.3 of quartz, which AFAIK does not have locality constraints, and I find myself now between a rock and a hard place.

On the quartz forums they recommend using the commercial Terracotta Enterprise 3.5 and Quartz (2.0) Where.

Has anyone solved this issue before?

Thank you.
Reply | Threaded
Open this post in threaded view
|

Re: Quartz plugin issues

Luis Muniz-2
A solution pointed out in the Terracotta Quartz forum is to define 2 different schedulers, one clustered and one local.

I guess to make that work in  the quartz plugin I would have to dig into the code.
I thought I'd check out the current snapshot version, 1.0-SNAPSHOT from github, but found that there were a ton of tests failing in this version.

By the way in the documentation the version 1.0-SNAPSHOT is recommended for grails 1.3 but there is no way to install it.

I reverted to 0.4-stable, but many tests fail in this branch too.

I feel sorry now to have looked under the hood, as my confidence in this plugin is in question now. :-)
Not trolling here, I can give time to contribute and help resolve this, but I find it disturbing that the only scheduling plugin for grails is in this state, even the stable version.

On Wed, Mar 30, 2011 at 11:31 AM, Luis Muniz <[hidden email]> wrote:
Hi,

I am deploying my grails application to a cluster and thus have to clusterize my quartz jobs.

However, some jobs mustn't be clusterized, some jobs need to be local to the node where they are aexecuted, and must run regardless of other jobs of teh same type being run on other nodes.
Apparently the grails quartz plugin uses version 1.7.3 of quartz, which AFAIK does not have locality constraints, and I find myself now between a rock and a hard place.

On the quartz forums they recommend using the commercial Terracotta Enterprise 3.5 and Quartz (2.0) Where.

Has anyone solved this issue before?

Thank you.

Reply | Threaded
Open this post in threaded view
|

Re: Quartz plugin issues

Sergey Nebolsin
Hi, Luis!

Sorry, I don't have experience in clustered Quartz setups, so cannot help here.

For the failing tests: yes, that's my bad, tests are obsolete and don't actually test something useful. I have a ticket titled like "Improve test coverage" but had not enough time to do it.

You can install the latest snapshot with 'grails install-plugin https://github.com/downloads/nebolsin/grails-quartz/grails-quartz-1.0-SNAPSHOT-469c6c7.zip'.

As usual, pull requests with some feature implementations or test improvements will be greatly appreciated :)

Cheers

On Wed, Mar 30, 2011 at 14:22, Luis Muniz <[hidden email]> wrote:
A solution pointed out in the Terracotta Quartz forum is to define 2 different schedulers, one clustered and one local.

I guess to make that work in  the quartz plugin I would have to dig into the code.
I thought I'd check out the current snapshot version, 1.0-SNAPSHOT from github, but found that there were a ton of tests failing in this version.

By the way in the documentation the version 1.0-SNAPSHOT is recommended for grails 1.3 but there is no way to install it.

I reverted to 0.4-stable, but many tests fail in this branch too.

I feel sorry now to have looked under the hood, as my confidence in this plugin is in question now. :-)
Not trolling here, I can give time to contribute and help resolve this, but I find it disturbing that the only scheduling plugin for grails is in this state, even the stable version.


On Wed, Mar 30, 2011 at 11:31 AM, Luis Muniz <[hidden email]> wrote:
Hi,

I am deploying my grails application to a cluster and thus have to clusterize my quartz jobs.

However, some jobs mustn't be clusterized, some jobs need to be local to the node where they are aexecuted, and must run regardless of other jobs of teh same type being run on other nodes.
Apparently the grails quartz plugin uses version 1.7.3 of quartz, which AFAIK does not have locality constraints, and I find myself now between a rock and a hard place.

On the quartz forums they recommend using the commercial Terracotta Enterprise 3.5 and Quartz (2.0) Where.

Has anyone solved this issue before?

Thank you.




--
Sergey Nebolsin
CTO at Prophotos.ru, Bestphotographer.ru and Fotoshkola.net