Uploaded image for project: 'mod-inn-reach'
  1. mod-inn-reach
  2. MODINREACH-397

Some Kafka Events are not processed properly during Initial contribution

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • TBD
    • Resolution: Done
    • None
    • None
    • None
    • Volaris Sprint 174, Volaris Sprint 175
    • 1
    • Volaris
    • TBD

    Description

      Overview:

      when the Initial contribution is started, as part of outbox implementation Kafka events are persisted in the job_execution_status table with status as READY.  Spring scheduler picks the record for processing only when it is in READY or RETRY status, 

      The status will gets changed to IN_PROGRESS before processing by the scheduler.

      After the above step , If the server is restarted immediately, the IN_PROGRESS records are not picked up by the scheduler for processing and as a result the records are not processed and Initial contribution is not ended up properly

      Steps to Reproduce:

      1. Log into rancher environment
      2. start the Initial contribution
      3. Now check the job_execution_status  table, you can find the new records and change anyone of the records status manually to IN_PROGRESS. 
      4. Now , restart the server. 
      5. Spring scheduler will not pick the record with IN_PROGRESS status

      Expected Results:

      1. when the scheduler started again, it needs to pickup the IN_PROGRESS record and complete the record processing

      Actual Results:

      Additional Information:
      We can change the status of IN_PROGRESS records to READY when the service is started. so that scheduler will pick the records which are in READY status

      Interested parties:

      GurleenKaur stevel IrinaP 

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Vignesh Vignesh Kalyanasundaram
                Vignesh Vignesh Kalyanasundaram
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases