Parallel EOD/EOI processing¶
This page explains how parallel EOD/EOI processing works in KX Sensors.
Parallel processing of EOD/EOI allows you to run EOD and EOI in parallel rather than serially in DBW. It's the default setting in KX Sensors, and strongly recommended whenever your ingestion volumes are high. If you deactivate parallel processing, DBW processes your EODs and EOIs serially; that is, during EOD, no EOIs are processed until your EOD is fully complete, at which time the dozen or so EOIs that have accumulated during this period are processed one after the other.
Parallel processing uses parent and child, or subtask, processes: kxsDBW is the parent process and the DBW subtask is the child. You configure parallel processing in the following systemParams.yaml attributes:
| Attribute | Description | Default |
|---|---|---|
eodDefer |
The number of minutes that start of EOD processing is deferred after the journal day has finished. Some queries may run faster if there is a minimum amount of data in IDB; by deferring, you set that minimum size. | 0 |
eodSubTask |
Whether or not parallel processing (that is, the DBZ subtask) is activated. Note! Killing the parent task automatically kills the subtask. |
Y |
dbzThreads |
The number of threads assigned to the DBZ subtask. When set to null (0Ni), DBZ is assigned the same number of threads as DBW. |
|
dbzTries |
Number of subtask attempts to process EOD/EOI. | 2 |
ntCallInterval |
Interval in milliseconds during which ntask processes attempt to reestablish a connection to their parent. | 250 |
ntCallRetries |
Maximum number of retries when attempting to connect to parent from ntask. | 3 |