October 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7075) [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/ISPN-7075?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos commented on ISPN-7075: ----------------------------------------------- Back porting ISPN-6857 > [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain > --------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7075 > URL: https://issues.jboss.org/browse/ISPN-7075 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Fix For: 9.0.0.Final, 8.2.5.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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7075) [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/ISPN-7075?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos updated ISPN-7075: ------------------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4592 (was: https://github.com/infinispan/infinispan/pull/4557, https://github.com/infinispan/infinispan/pull/4558) > [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain > --------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7075 > URL: https://issues.jboss.org/browse/ISPN-7075 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Fix For: 9.0.0.Final, 8.2.5.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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7075) [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/ISPN-7075?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos updated ISPN-7075: ------------------------------------------ Status: Open (was: New) > [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain > --------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7075 > URL: https://issues.jboss.org/browse/ISPN-7075 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Fix For: 9.0.0.Final, 8.2.5.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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7075) [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/ISPN-7075?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos updated ISPN-7075: ------------------------------------------ Status: Pull Request Sent (was: Open) > [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain > --------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7075 > URL: https://issues.jboss.org/browse/ISPN-7075 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Fix For: 9.0.0.Final, 8.2.5.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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7075) [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/ISPN-7075?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos reassigned ISPN-7075: --------------------------------------------- Assignee: Panagiotis Sotiropoulos (was: Dan Berindei) > [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain > --------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7075 > URL: https://issues.jboss.org/browse/ISPN-7075 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Fix For: 9.0.0.Final, 8.2.5.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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7075) [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain

by Panagiotis Sotiropoulos (JIRA)

Panagiotis Sotiropoulos created ISPN-7075: --------------------------------------------- Summary: [8.1.x] : OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain Key: ISPN-7075 URL: https://issues.jboss.org/browse/ISPN-7075 Project: Infinispan Issue Type: Bug Affects Versions: 8.1.0.Final Reporter: Panagiotis Sotiropoulos Assignee: Dan Berindei Fix For: 9.0.0.Final, 8.2.5.Final 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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7074) Indexed entities inheritance does not copy set

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7074?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7074: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4591 > Indexed entities inheritance does not copy set > ---------------------------------------------- > > Key: ISPN-7074 > URL: https://issues.jboss.org/browse/ISPN-7074 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Alpha4, 8.2.4.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1, 9.0.0.Final, 8.2.5.Final > > > The indexed entities configuration attribute does not provide a copier so, in the case of inheritance, all configurations share the same set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7074) Indexed entities inheritance does not copy set

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-7074: ------------------------------------- Summary: Indexed entities inheritance does not copy set Key: ISPN-7074 URL: https://issues.jboss.org/browse/ISPN-7074 Project: Infinispan Issue Type: Bug Affects Versions: 8.2.4.Final, 9.0.0.Alpha4 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.0.0.Beta1, 9.0.0.Final, 8.2.5.Final The indexed entities configuration attribute does not provide a copier so, in the case of inheritance, all configurations share the same set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7074) Indexed entities inheritance does not copy set

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7074?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7074: ---------------------------------- Status: Open (was: New) > Indexed entities inheritance does not copy set > ---------------------------------------------- > > Key: ISPN-7074 > URL: https://issues.jboss.org/browse/ISPN-7074 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Alpha4, 8.2.4.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1, 9.0.0.Final, 8.2.5.Final > > > The indexed entities configuration attribute does not provide a copier so, in the case of inheritance, all configurations share the same set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7058) Server and WildFly module still depend on the JAXB module

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7058?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7058: -------------------------------------- Fix Version/s: 8.2.5.Final > Server and WildFly module still depend on the JAXB module > --------------------------------------------------------- > > Key: ISPN-7058 > URL: https://issues.jboss.org/browse/ISPN-7058 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1, 9.0.0.Final, 8.2.5.Final > > > The use of JAXB for parsing the configuration was removed a long time ago. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2016