Worker Processes - org-z2env-worker » History » Version 2
Henning Blohm, 26.08.2015 15:00
| 1 | 1 | Henning Blohm | h1. Worker Processes (org.z2env.worker) |
|---|---|---|---|
| 2 | 2 | Henning Blohm | |
| 3 | A worker process component, when _prepared_ starts a new z2 Java process that keeps running until stopped or some configured Runnable or Main class completes. |
||
| 4 | |||
| 5 | ??The point in using worker process components is that this allows you to configure process configuration such as heap size via a component declaration in a central repository rather than using some scripting rules. Also, when using worker processes, the home process can be used to make sure actual application processes get restarted, in case of process crashes. Finally, in nontrivial and distributed scenarios, where a number of different node types are required, starting any combination of those from a single home process makes scale out configuration simple and robust.?? |
||
| 6 | |||
| 7 | A worker process component is declared by specifying some process configuration and some target states, e.g. like this: |
||
| 8 | |||
| 9 | <pre><code class="bash"> |
||
| 10 | org.z2env.component.type=org.z2env.worker |
||
| 11 | worker.process.vmOptions=-Xmx1024M |
||
| 12 | worker.states=mymodule/workerUp |
||
| 13 | </code></pre> |
||
| 14 | |||
| 15 | or like this, in case the component *mymodule/main* is a main component or supplies a Runnable. |
||
| 16 | |||
| 17 | <pre><code class="bash"> |
||
| 18 | org.z2env.component.type=org.z2env.worker |
||
| 19 | worker.process.vmOptions=-Xmx1024M |
||
| 20 | worker.states=mymodule/workerUp |
||
| 21 | worker.main=mymodule/main |
||
| 22 | </code></pre> |