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

Handle not initialized tenant

    XMLWordPrintable

Details

    • Falcon Sprint 121
    • 1
    • Falcon

    Description

      Purpose/Overview:

      Currently, if mod-search is not initialized for the tenant, the error will be thrown, which affects message processing for other tenants.

      Also current retry settings for failed messages are:

      application:
  kafka:
    retry-interval-ms: 20000
    retry-delivery-attempts: 10

      This leads that initial bulk processed with a time equal to:

      10 * 20 sec = 200 sec

      and then, if it's failing every message is processed with the same amount of time. So the gracefully handled bulk processed with time:

      200s + 50 (amount of messages in bulk) * 10 * 20 sec = 10200 sec = 170 min

      This value must be decreased to 10 minutes to not stop the processing of messages for a long time. The current implementation will log every unprocessed message.

      Requirements/Scope:

      1. If mod-search is not initialized for the tenant, the error should not be thrown.
      2. Kafka settings: retry-interval-ms and retry-delivery-attempts must be decreased
      3. retry-interval-ms must be set to 2000
      4. retry-delivery-attempts must be set to 6
      5. Make these options configurable by setting environment variables: KAFKA_RETRY_INTERVAL_MS and KAFKA_RETRY_DELIVERY_ATTEMPTS

      Acceptance criteria:

      • Integration and unit tests are passed through

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-3046 NFR: Inventory. Swap from search tool PostgreSQL to Elasticsearch

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

            New Feature - New feature requests UXPROD-3271 NFR: Look up instance plug-in. Swap from search tool PostgreSQL to Elasticsearch

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

            New Feature - New feature requests UXPROD-3430 Inventory. Implement Facets on filtering (Instance, Holdings, Item) when using Elasticsearch

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

            Task - A task that needs to be done. UIIN-1566 convert existing search/filter endpoints to use ES paths

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

            Task - A task that needs to be done. UIIN-1631 Convert Action menu: Save instances UUIDs from existing search/filter endpoints to use ES paths

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

            Activity

              People

                pavel_filippov Pavel Filippov
                pavel_filippov Pavel Filippov
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases