Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Master indexing nodes fail to lookup lazily initialized IndexManager instances

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.

Activity

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created June 2, 2015 at 10:53 AM
Updated May 11, 2017 at 7:35 AM
Resolved April 21, 2017 at 10:02 AM

Flag notifications