We're updating the issue view to help you get more done. 

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.

Environment

None

Status

Assignee

Yoann Rodière

Reporter

Sanne Grinovero

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Components

Fix versions

Affects versions

5.3.0.CR1
4.5.3.Final
5.1.1.Final
4.4.6.Final
5.0.1.Final

Priority

Critical