Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-11710

MassIndexer timeouts after 4 minutes

    XMLWordPrintable

Details

    Description

      The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded).
      Until it is possible to cancel the MassIndexer (see ISPN-11735), it should not timeout.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-11735 Supporting cancellation in the ClusterExecutor

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New

          Activity

            People

              gfernand@redhat.com Gustavo Fernandes (Inactive)
              gfernand@redhat.com Gustavo Fernandes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: