[JBoss JIRA] (ISPN-6857) OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6857?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6857:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 8.1.6.Final
Resolution: Done
> OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6857
> URL: https://issues.jboss.org/browse/ISPN-6857
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Final, 9.0.0.Alpha4, 8.2.4.Final
> Reporter: Marek Posolda
> Assignee: Dan Berindei
> Fix For: 9.0.0.Final, 8.2.5.Final, 8.1.6.Final
>
> Attachments: OutdatedTopologyExceptionReproducerTest.java
>
>
> I have the following setup:
> - 2 nodes in cluster with mode INVALIDATION_SYNC. No-transaction cache.
> - Node1 is started
> - Called "cache.remove" on some key on node1. At the same time, node2 is starting, which is causing topology change.
> - The "cache.remove" call on node1 is throwing OutdatedTopologyException.
> I found the cause is that StateTransferInterceptor is not added in InterceptorChain during INVALIDATION mode. It's just available during REPLICATION or DISTRIBUTED modes - https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
> Indeed when I manually added StateTransferInterceptor to my invalidation cache:
> {code}
> invalidationConfigBuilder.customInterceptors()
> .addInterceptor()
> .before(NonTransactionalLockingInterceptor.class)
> .interceptorClass(StateTransferInterceptor.class);
> {code}
>
> I can see that issue is gone as OutdatedTopologyException is catched and command is retried with new topology.
> I am attaching the Java unit test for reproducing issue. On my laptop when I run it, I can almost always simulate the issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (ISPN-7077) Export dependencies in the embedded modules
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-7077?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reassigned ISPN-7077:
---------------------------------------
Assignee: Gustavo Fernandes
> Export dependencies in the embedded modules
> -------------------------------------------
>
> Key: ISPN-7077
> URL: https://issues.jboss.org/browse/ISPN-7077
> Project: Infinispan
> Issue Type: Enhancement
> Components: WildFly modules
> Affects Versions: 9.0.0.Alpha4
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> Users need to list all dependencies one by one, and this is usually done by trial and error. Example, here's the current list of deps needed to do queries over hotrod when using modules:
> {code:java}
> "org.infinispan.client.hotrod:ispn-9.0 services, org.infinispan.protostream:ispn-9.0 services, org.infinispan.query.dsl:ispn-9.0 services, org.infinispan.commons:ispn-9.0 services"
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (ISPN-7077) Export dependencies in the embedded modules
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-7077?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-7077:
------------------------------------
Description:
Users need to list all dependencies one by one, and this is usually done by trial and error. Example, here's the current list of deps needed to do queries over hotrod when using modules:
{code:java}
"org.infinispan.client.hotrod:ispn-9.0 services, org.infinispan.protostream:ispn-9.0 services, org.infinispan.query.dsl:ispn-9.0 services, org.infinispan.commons:ispn-9.0 services"
{code}
> Export dependencies in the embedded modules
> -------------------------------------------
>
> Key: ISPN-7077
> URL: https://issues.jboss.org/browse/ISPN-7077
> Project: Infinispan
> Issue Type: Enhancement
> Components: WildFly modules
> Affects Versions: 9.0.0.Alpha4
> Reporter: Gustavo Fernandes
>
> Users need to list all dependencies one by one, and this is usually done by trial and error. Example, here's the current list of deps needed to do queries over hotrod when using modules:
> {code:java}
> "org.infinispan.client.hotrod:ispn-9.0 services, org.infinispan.protostream:ispn-9.0 services, org.infinispan.query.dsl:ispn-9.0 services, org.infinispan.commons:ispn-9.0 services"
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (ISPN-5469) Remote-executor threads should not block during RPCs
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5469?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5469:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.Final
Resolution: Done
> Remote-executor threads should not block during RPCs
> ----------------------------------------------------
>
> Key: ISPN-5469
> URL: https://issues.jboss.org/browse/ISPN-5469
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 7.2.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.0.0.Beta1, 9.0.0.Final
>
>
> This is particularly important in non-transactional caches, where the primary owner has to forward a command to the backup owners. The remote-executor thread on the primary should not be blocked while waiting for the backup responses, and instead process other commands.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months