Uploaded image for project: 'mod-search'
  1. mod-search
  2. MSEARCH-155

Gracefully handle Kafka message processing failures

    XMLWordPrintable

    Details

    • Template:
      Falcon user story template
    • Sprint:
      Falcon Sprint 118, Falcon Sprint 119
    • Story Points:
      0.5
    • Development Team:
      Falcon

      Description

      Purpose/Overview:

      If the notification message cannot be processed and the batch saving is failed. The batch should be divided into single messages and process one by one. For each of these single message processing, there should be a retried 3 times in case of error. After 3 unsuccessful retries, the message should be logged.

      This approach allows mod-search to avoid "poison pill" behavior when one "bad" message can stop the whole system.

      Approach:

      Implement batch process which will allow to a system process to retry batch 3 times and then split this batch to a single message and retry them 3 times too. In case of error - the failed message must be logged.

      Acceptance criteria:

      • A batch of messages must be retried 3 times and then it must be split
      • A single message of the batch must be retried 3 times and then logged
      • Kafka partition offset must be moved after logging failed message and processing must continue normally
      • Integration and unit tests are added

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                pavel_filippov Pavel Filippov
                Reporter:
                pavel_filippov Pavel Filippov
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases