From c762eb18c16f5cf05ac79312bd24a7a8ab1aa664 Mon Sep 17 00:00:00 2001 From: maximesson Date: Thu, 4 Apr 2019 14:43:43 +0000 Subject: Update documentation Change-Id: I2df7480401fe0371b7458962ac3535a00f287919 Issue-ID: DCAEGEN2-1389 Signed-off-by: maximesson --- docs/sections/services/dfc/architecture.rst | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'docs/sections/services/dfc/architecture.rst') diff --git a/docs/sections/services/dfc/architecture.rst b/docs/sections/services/dfc/architecture.rst index 1ee922af..73597541 100644 --- a/docs/sections/services/dfc/architecture.rst +++ b/docs/sections/services/dfc/architecture.rst @@ -6,7 +6,8 @@ Architecture Introduction """""""""""" -DataFile Collector (DFC) is a part of DCAEGEN2. Some information about DFC and the reasons of its implementation can be found here: `5G bulk PM wiki page`_. +DataFile Collector (DFC) is a part of DCAEGEN2. Some information about DFC and the reasons of its implementation can be +found here: `5G bulk PM wiki page`_. .. _5G bulk PM wiki page: https://wiki.onap.org/display/DW/5G+-+Bulk+PM @@ -29,3 +30,13 @@ Interaction """"""""""" DFC will interact with the DMaaP Message Router and with the Data Router via secured protocol, using json files. So far, the implemented protocols are sftp and ftp(e)s. + +Retry mechanism +""""""""""""""" +DFC is designed to retry downloading and publishing of files in order to recover from temporary faults. +Each time an event is received, DFC will try to download and and publish each previously unpublished file in the event. +The event is received from the Message Router (MR), the files are fetched from a PNF and are published to Data Router +(DR). +Both fetching of a file and publishing is retried a number of times with an increasing delay between each attempt. +After a number of attempts, the DFC will log an error message and give up. Failing of processing of one file does not +affect the handling of others. \ No newline at end of file -- cgit 1.2.3-korg