[infinispan-issues] [JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

[Gustavo Fernandes (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031749#comment-13031749 ] 

Gustavo Fernandes commented on ISPN-3835:
-----------------------------------------

[~sannegrinovero] Is this still relevant? If so, any further info (stack trace, forum, steps to reproduce, etc) available?

> 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: Embedded Querying
>    Affects Versions: 6.0.0.Final
>            Reporter: Sanne Grinovero
>            Assignee: Gustavo Fernandes
>            Priority: Critical
>              Labels: 64QueryBlockers
>             Fix For: 7.1.0.CR1
>
>
> 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 was sent by Atlassian JIRA
(v6.3.11#6341)