<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "Distributed Quartz with HA"]]></title>
		<link>http://forums.terracotta.org/forums/posts/list/17.page</link>
		<description><![CDATA[Latest messages posted in the topic "Distributed Quartz with HA"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>Distributed Quartz with HA</title>
				<description><![CDATA[ Hi, just looking into Quartz. I'm looking for a distributed and HA solution. 

I'd like to be able to submit jobs by different servers running on different machines, and have them processed by "whoever". Eg, if a server on a machine submitted a job, but then that particular machine crashed before the job executed, one of the other servers should be able to execute that job.


Now, will this work out of the box if i just configure a JDBC store?

If so, i'd rather avoid having to use a DB. Instead, some sort of "clustered memory" solution.

Is terracota the only current solution available for this sort of thing? But terracota costs money, right?

Also, we currently use Oracle coherence, so it'd be nice to just leverage that for the jobstore. Does anybody know of a jobstore implementation that uses oracle coherence?

Thx.]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/3457.page#19321</guid>
				<link>http://forums.terracotta.org/forums/posts/list/3457.page#19321</link>
				<pubDate><![CDATA[Tue, 13 Apr 2010 19:17:19]]> GMT</pubDate>
				<author><![CDATA[ jack36]]></author>
			</item>
			<item>
				<title>Re:Distributed Quartz with HA</title>
				<description><![CDATA[ 

The JDBC-JobStore clustering solution should do as you want "out of the box" - just set isClustere=true in the quartz properties for the job store.


The only other implementation (that I know of) with clustering is the TerracottaJobStore.

Terracotta does NOT cost money for most setups.  You can make an HA Terracotta setup with 1 Active and N Passive (aka "standby" - which become active when the active dies) Terractotta servers without paying licensing.  (Note that I'm talking about the terracotta servers here, not the TerracottaJobStore - which is free for any number of active quartz nodes).  The active-passive TC server setup would be adequate for most anyone using Terracotta for Quartz. 

Terracotta only costs money for:  1) support services, 2) running an array of active servers (for greater scaling).

]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/3457.page#19322</guid>
				<link>http://forums.terracotta.org/forums/posts/list/3457.page#19322</link>
				<pubDate><![CDATA[Tue, 13 Apr 2010 19:36:38]]> GMT</pubDate>
				<author><![CDATA[ jhouse]]></author>
			</item>
			<item>
				<title>Re:Distributed Quartz with HA</title>
				<description><![CDATA[ How would i configure 1-active/n-passive? In the config props for quartz, when i configure terracota, i have to specify a specific host:port. So presumably that would be the host:port of the active; how would it fail-over to one of the passives?

Thx.]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/3457.page#19332</guid>
				<link>http://forums.terracotta.org/forums/posts/list/3457.page#19332</link>
				<pubDate><![CDATA[Tue, 13 Apr 2010 23:29:07]]> GMT</pubDate>
				<author><![CDATA[ jack36]]></author>
			</item>
			<item>
				<title>Distributed Quartz with HA</title>
				<description><![CDATA[ Check out the Terracotta product docs here:

http://www.terracotta.org/documentation/ga/product-documentation-1page.html

There is a chapter on Quartz and a chapter on the Terracotta platform that talks about HA, servers, failover, etc.]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/3457.page#19363</guid>
				<link>http://forums.terracotta.org/forums/posts/list/3457.page#19363</link>
				<pubDate><![CDATA[Wed, 14 Apr 2010 09:00:56]]> GMT</pubDate>
				<author><![CDATA[ ilevy]]></author>
			</item>
			<item>
				<title>Re:Distributed Quartz with HA</title>
				<description><![CDATA[ The doc link should be the best place to learn how to configure the active/passive terracotta servers. 

Over on client side (where quartz is running), you probably want to list all of your terracotta servers. Something like:

...jobstore.tcConfigURL="host1:9510,host2:9510"

That list of URLs doesn't necessary define the terracotta servers. That is a list of possible config sources. "host1:9510" is actually just shorthand for http://host1:9510/config". You can hit that URL in a web browser and see the tc-config.xml that the clustered job store will use. You want to list all of your servers so that you can always start your clients no matter which terracotta servers happen to be running at the time. 

I know of no quartz job store based on Oracle coherence. ]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/3457.page#19375</guid>
				<link>http://forums.terracotta.org/forums/posts/list/3457.page#19375</link>
				<pubDate><![CDATA[Wed, 14 Apr 2010 11:15:27]]> GMT</pubDate>
				<author><![CDATA[ teck]]></author>
			</item>
	</channel>
</rss>