Uploaded image for project: 'mod-source-record-manager'
  1. mod-source-record-manager
  2. MODSOURMAN-899

Do not process chunks when the DI job is stopped

    XMLWordPrintable

Details

    • Folijet Sprint 159
    • 5
    • Folijet
    • Orchid (R1 2023)

    Description

      Currently, when a user cancels job DI continues to process chunks related to this job.
      In RawMarcChunksKafkaHandler and StoredRecordChunksKafkaHandler get jobExecutionId from Kafka headers, check JobExecution status, if canceled or deleted (empty result) - skip processing of the chunk (DI_ERROR messages NOT needed) without deserializing (unpacking) the chunks.

      Check impact on job progress tracking - add same logic in DataImportKafkaHandler (DI_COMPLETE and DI_ERROR messages). Check behavior of FlowControl, create separate task to resolve any issues.

      This method will increase the performance of the DI and reduce the load on the CPU.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Task - A task that needs to be done. MODSOURMAN-934 Release v3.6.0 (R1 Orchid)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            defines

            New Feature - New feature requests UXPROD-3725 NFR: Data Import Technical, NFR, & Misc work (Orchid R1 2023)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is cloned by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURMAN-982 SPIKE: Investigate why chunks continue processing after DI job is completed

            • P2 - normal priority level, must be included in the current development cycle
            • Open
            relates to

            Task - A task that needs to be done. MODSOURMAN-933 Prevent jobs from hanging when cancelled job is deleted before BG processing is finished

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODDATAIMP-428 Cancelled data import jobs sometimes continue on to completion

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-940 DI Jobs stuck when selecting a wrong profile

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURMAN-956 Stop processing the job with incorrect profile

            • P2 - normal priority level, must be included in the current development cycle
            • Open

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-970 Jobs run immediately after canceled job take excess time

            • P2 - normal priority level, must be included in the current development cycle
            • Open

            Activity

              People

                Kyrylo Shulzhenko Kyrylo Shulzhenko
                afedasiuk Aliaksandr Fedasiuk
                Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases