• New Feature
  • Status: Open
  • 2 Major
  • Resolution:
  • prodmgmt
  • Reporter: jhartley
  • January 07, 2007
  • 3
  • Watchers: 3
  • March 19, 2010

Description

Motivation: Target Quartz Job Scheduler (http://www.opensymphony.com/quartz/) support to increase Terracotta’s transparency and add to the portfolio of Terracotta clustered frameworks.

Clustering Quartz Requirements: * Fail-over - if one node is running a job, and fails, the job will run on another node * Load balancing of jobs - to execute on the first (or “most”) available node * “Pinning” of jobs - to execute on a specific node * “Ubiquitous” jobs - to execute on every node * “Appropriating” of jobs - to execute on the node that has the given capabilities the job requires

Use Case: We could implement a simple use case like a Tournament system which should cover basic scheduling capabilities and test fail-over and scalability (through load balancing). Pinning would involve running some maintenance jobs like vacuuming a database. Ubiquitous jobs could be something like refreshing a local (not shared) cache. Appropriate jobs are kind of like pinning and could involve things like creating backups of a datastore.

Notes: Clustering Quartz may be as simple as clustering RAMJobStore (http://www.opensymphony.com/quartz/api/org/quartz/simpl/RAMJobStore.html).

Comments

Nathaniel Harward 2007-02-28

This simply won’t happen for Moraga, no time left.

Fiona OShea 2007-03-01

Assigning back to PM. We will probably want to fit this in Noriega

Nathaniel Harward 2007-06-05

Just adding to the mix, there is a forum post at http://forums.terracotta.org/forums/posts/list/178.page#969, Kunal has posted a sample tc-config.xml file that might just work or need a little tweaking.

Fiona OShea 2007-12-03

Assigning to DRB as Nitin has said in response to an email from Orion Yes, we should change this. I tested it for stability in many scenarios.

Nitin

—–Original Message—– From: Orion Letizi [mailto:[email protected]] Sent: Tuesday, November 20, 2007 1:20 AM To: Nitin Jain Cc: sales; fieldeng; pm Subject: Re: [Fieldeng] Clustering Quartz

Should we change this:

https://jira.terracotta.org/jira//browse/CDV-53

and this:

http://www.terracotta.org/confluence/display/integrations/Quartz

? Or, is this still experimental?

Fiona OShea 2007-12-03

—–Original Message—– From: [email protected] [mailto:[email protected]] On Behalf Of Sreenivasan Iyer Sent: Tuesday, November 20, 2007 10:21 AM To: Steven Harris Cc: Orion Letizi; pm; Nitin Jain; sales; fieldeng Subject: Re: [Pm] [Fieldeng] Clustering Quartz

Yes. Centric-CRM will use this (+ 1 other customer we sent this too). We can support it for now - but at some point we need the conversation around when (Pacheco, Quintara?) it becomes officially certified. Thanks

—– Original Message —– From: “Steven Harris” [email protected] To: “Orion Letizi” [email protected] Cc: “pm” [email protected], “Nitin Jain” [email protected], “sales” [email protected], “fieldeng” [email protected] Sent: Tuesday, November 20, 2007 10:11:16 AM (GMT-0800) America/Los_Angeles Subject: Re: [Pm] [Fieldeng] Clustering Quartz

I think it should be in the forge and develop and mature. That’s what the forge is for :-)