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

Out of order events produced when using the MassIndexer with async backend

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • 7.2.0.Beta2, 7.1.1.Final
    • 7.2.0.CR1, 7.2.0.Final
    • None
    • None

    Description

      When using async indexing backend on DIST caches with shared index (InfinispanIndexManager), the MassIndexer fails to re-index all the entries, if it is run from a node that is not
      the indexing master.

      Normally the operation sequence of the MassIndexer in the above configuration, for a two node cluster is:

      • Purge the index
      • Send index job to node A and to node B
      • Flush

      Given the backend is async, all index commands are sent to the master RPC-wise asynchronously, and so a reorder can occur and produce like:

      • Send index job to node A
      • Purge
      • Send index job to node B
      • Flush

      Causing previously re-indexed entries to be wiped

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: