Job Forking

From Obsidian Scheduler
Revision as of 03:33, 30 January 2015 by Craig (talk | contribs) (Created page with "As of Obsidian 3.0.0, Obsidian can run each job in its own JVM. This allows for a number of possibilities, not the least of which is supporting dynamic changes to your deploye...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

As of Obsidian 3.0.0, Obsidian can run each job in its own JVM. This allows for a number of possibilities, not the least of which is supporting dynamic changes to your deployed, compiled jobs, also known as hot-swapping of JARs. In theory, you could even specialize classpaths on a per job basis by customizing the executions scripts provided.

To ensure backwards compatibility and controlled usage of this functionality, it is disabled by default for the cluster. Standalone deployments are configured to have it enabled, but are not active until you enable it for the cluster.

Enabling Job Forking

First you must enable the functionality on the cluster. This is a System Parameter found in the JobSpawner category.

You may enable it via the Admin UI, via one of the provided APIs (Embedded API or REST API) or the Initializing and Restoring support.

Once you've done that, you'll need to enable it on each desired node. This is done via a properties value entry.

com.carfey.obsidian.jvmJobForkingEnabledOnThisNode=true

Retrieved from "https://wiki.obsidianscheduler.com/doc/index.php?title=Job_Forking&oldid=2135"