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

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

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.2.0.Beta2, 7.1.1.Final
    • Fix Version/s: 7.2.0.CR1, 7.2.0.Final
    • Component/s: None
    • Labels:
      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

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                gustavonalle Gustavo Fernandes
                Reporter:
                gustavonalle Gustavo Fernandes
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: