Uploaded image for project: 'Hibernate Search'
  1. HSEARCH-1886

Master indexing nodes fail to lookup lazily initialized IndexManager instances

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 4.4.6.Final, 4.5.3.Final, 5.0.1.Final, 5.1.1.Final, 5.3.0.CR1
    • Fix Version/s: 5.8.0.Beta2
    • Component/s: backend
    • Labels:
      None

      Description

      As discussed on https://forum.hibernate.org/viewtopic.php?f=9&t=1032144

      A JMS master node can receive messages to update an index named "X", while the IndexManager for X is defined by a DynamicShardingStrategy.
      The current code is not triggering the IndexManager initialization, but rather fails reporting that this IndexManager isn't found.

      A possible workaround is to trigger initialization of all indexes, for example running a full-text query on all indexes right after boot but this would need to happen before the first message is processed.

        Attachments

          Issue links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: