blob: 032b4b143b7e20b8c1999cb194b535406326fc62 [file] [log] [blame]
DylanB95ESTdc656472022-08-08 15:22:54 +01001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2.. http://creativecommons.org/licenses/by/4.0
3.. Copyright (C) 2022 Nordix Foundation
4
5.. DO NOT CHANGE THIS LABEL FOR RELEASE NOTES - EVEN THOUGH IT GIVES A WARNING
emacleeb176de22022-08-31 15:53:10 +01006
7.. _cpsScheduledProcesses:
DylanB95ESTdc656472022-08-08 15:22:54 +01008
9
10CPS Scheduled Processes
11#######################
12
13.. toctree::
14 :maxdepth: 1
15
16Introduction
17============
18
19The following section is a list of the current scheduled processes running within the CPS system.
20
21Module Sync
22-----------
23The module sync is a user :ref:`configurable timed process<additional-cps-ncmp-customizations>`,
24which is set to search for CM-Handles within CPS with an *'ADVISED'* state.
25Once the CM-Handle(s) is processed by the module sync, the CM-Handle state is then set to *'READY'*, if the process completes successfully.
26If for any reason the module sync fails, the CM-Handle state will then be set to *'LOCKED'*,
27and the reason for the lock will also be stored within CPS.
28
29Data Sync
30---------
31The data sync is a user :ref:`configurable timed process<additional-cps-ncmp-customizations>`,
32which is set to search for CM-Handles with a sync state of *'UNSYNCHRONIZED'*.
33Once the CM-Handle(s) with a sync state of *'UNSYNCHRONIZED'* is processed by the data sync,
34the CM-Handle sync state is then set to *'SYNCHRONIZED'*, if the process completes successfully.
35If the data sync fails, the CM-Handle sync state will remain as *'UNSYNCHRONIZED'*, and will be re-attempted.
36
37Retry Mechanism
38---------------
39The retry mechanism is a user :ref:`configurable timed process<additional-cps-ncmp-customizations>`,
40which is used to search for CM-Handles which are currently in a *'LOCKED'* state.
41If the CM-Handle is ready to be retried then, the CM-Handle(s) in a *'LOCKED'* state is processed by the retry mechanism,
42the CM-Handle state is then set to *'ADVISED'*.
43Whether the CM-Handle is ready to be retried is dependent on both the number of attempts to sync the CM-Handle,
44and the last update time of the CM-Handle state.
45With each new attempt to unlock the CM-Handle, the time until the CM-Handle can next be retried is doubled.