...
The product without any dependency is sometimes referred to as “master” or ”base” product.
In case of distributed/parallel calculations:
It can happen that “A” and “B” will be calculated on different nodes. Nevertheless, the same rules apply – if the logic starts calculation of the dependent product “B” and the price of the master product “A” is not yet available, the logic will mark the line as dirty, and once the first pass finishes on all nodes, then the system will start the second pass for all “dirty” lines (possibly again distributed across multiple nodes).
Failure in a dirty pass calculation will leave the item dirty. In case of permanent failure, the dirty pass is recalculated until the maximum number of passes is reached. Sometimes, it is preferable not to retry but to mark the item as clean in case of a calculation error. This special behavior is optional and can be configured on a per-instance basis (on a cluster level), defaulting to the current behavior. Set the calculationTasks.alwaysCleanItems (
<alwaysCleanItems>false</alwaysCleanItems>) totrueto mark all items as clean upon a calculation failure – then the following dirty runs will not start.Keep in mind that keys within the map being cached are converted to String in the multi-pass calculation (for example, when using the
libs.SharedLib.CacheUtils.getOrSetto store the data in the cache).
Process Sample
...
Technical Implementation
...