StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POquartz scheduler clustering
primarykey
Id
10983666
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-11T16:01:26.020
FavoriteCount
0
LastActivityDate
2012-06-11T16:53:59.237
LastEditDate
2012-06-11T16:53:59.237
LastEditorUserId
405514
OwnerUserId
405514
ParentId
0
PostTypeId
1
Score
1
ViewCount
12601
LastEditorDisplayName
text
Body
I have a 2 node HA server. Node 1 is active and node 2 is standby. I have made one application and used the quartz api to do clustering. I have made all the tables in the db. Now do i need to run the module in both the nodes or jst node 1 so that when the node 1 goes down the application automatically starts in node 2. The trigger and the job name should be same or different while running the module in both the nodes? <h2>Quartz.properties:</h2> org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool org.quartz.threadPool.threadCount = 10 org.quartz.threadPool.threadPriority = 5 org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread = true -- Using RAMJobStore -- if using RAMJobStore, please be sure that you comment out -- org.quartz.jobStore.tablePrefix, org.quartz.jobStore.driverDelegateClass, org.quartz.jobStore.dataSource -org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore -- Using JobStoreTX -- Be sure to run the appropriate script(under docs/dbTables) first to create database/tables org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX -- Using DriverDelegate org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.StdJDBCDelegate --New conf for Clustering org.quartz.jobStore.isClustered = true org.quartz.jobStore.clusterCheckinInterval = 20000 org.quartz.scheduler.instanceId = AUTO org.quartz.scheduler.instanceId = AUTO org.quartz.scheduler.instanceName = MyClusteredScheduler -- Configuring JDBCJobStore with the Table Prefix org.quartz.jobStore.tablePrefix = QRTZ_ -- Using datasource org.quartz.jobStore.dataSource = qzDS -- Define the datasource to use org.quartz.dataSource.qzDS.driver = oracle.jdbc.driver.OracleDriver org.quartz.dataSource.qzDS.URL = jdbc:oracle:thin:@10.172.16.147:1521:emadb0 org.quartz.dataSource.qzDS.user = BLuser org.quartz.dataSource.qzDS.password = BLuser org.quartz.dataSource.qzDS.maxConnections = 30 <h2>-----------------------</h2>
Tags
<quartz-scheduler>
Title
quartz scheduler clustering
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USkaka
UserOwnerUserId
1. USkaka
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.