[
https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-3835:
-------------------------------
Fix Version/s: 7.0.0.Alpha1
(was: 6.0.1.Final)
Index Update command is processed before the registry listener is
triggered
---------------------------------------------------------------------------
Key: ISPN-3835
URL:
https://issues.jboss.org/browse/ISPN-3835
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 6.0.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 7.0.0.Alpha1
When using the InfinispanIndexManager backend the master node might receive an index
update command about an index which it hasn't defined yet.
Index definitions are triggered by the type registry, which in turn is driven by the
ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are
sending update requests before the master has processed the configuration event.
This leads to index update commands to be lost (with a stacktrace logged)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira