November 2014 - infinispan-issues

[JBoss JIRA] (ISPN-5011) CacheManager not stopping when search factory not initialized

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5011?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5011: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3100, https://github.com/infinispan/infinispan/pull/3104 > CacheManager not stopping when search factory not initialized > ------------------------------------------------------------- > > Key: ISPN-5011 > URL: https://issues.jboss.org/browse/ISPN-5011 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > > The situation can be reproduced in a simple test: > {code} > @Test > public void testStartAndStopWithoutIndexing() { > EmbeddedCacheManager cacheManager = ... // With indexing enabled, using infinispan directory > cacheManager.getCache(); > cacheManager.stop(); > assertEquals(ComponentStatus.TERMINATED, cacheManager.getStatus()); > } > {code} > The issue is that query related caches are lazily created, and the stop( ) method fails with NPE -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5011) CacheManager not stopping when search factory not initialized

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5011?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5011: -------------------------------- Status: Open (was: New) > CacheManager not stopping when search factory not initialized > ------------------------------------------------------------- > > Key: ISPN-5011 > URL: https://issues.jboss.org/browse/ISPN-5011 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > > The situation can be reproduced in a simple test: > {code} > @Test > public void testStartAndStopWithoutIndexing() { > EmbeddedCacheManager cacheManager = ... // With indexing enabled, using infinispan directory > cacheManager.getCache(); > cacheManager.stop(); > assertEquals(ComponentStatus.TERMINATED, cacheManager.getStatus()); > } > {code} > The issue is that query related caches are lazily created, and the stop( ) method fails with NPE -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4444) After state transfer, a node is able to read keys it no longer owns from its data container

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4444?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4444: ------------------------------------ [~pruivo] I think I have missed something in the bug description. If the CH_UPDATE command is delayed on the old owner, the new owners might update the key without the old owner knowing, and a locality check on the old owner won't help. I remember one thing that struck me when reading the Raft algorithm was that they install configuration changes symmetrically, in 3 phases. We might need to do the same for our rebalance: start a rebalance with {{read_ch=old, write_ch=old+new}}, when the new owners have all the data install {{read_ch=new, write_ch=old+new}}, and finally {{read_ch=new, write_ch=new}}. Old cache entries are removed during the 2nd topology update, and further writes should be ignored, in order for this to work. > After state transfer, a node is able to read keys it no longer owns from its data container > ------------------------------------------------------------------------------------------- > > Key: ISPN-4444 > URL: https://issues.jboss.org/browse/ISPN-4444 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 7.1.0.Alpha1 > > > When state transfer ends and each node receives a CH_UPDATE command from the coordinator, it first installs the new topology and then it starts invalidating entries it no longer owns. > However, there are two cases when the node can still read its stale values: > 1. If L1 is enabled, it will look in the local DataContainer first, regardless of the key's location. > 2. If L1 is disabled, but the key was removed on the new owners, the node will still look up the key in the local DataContainer after receiving a null response. > The problem can be reproduced with {{TxReadAfterLosingOwnershipTest}} and its subclasses, by replacing the {{operation.update(cache(1));}} line with {{operation.update(cache(0));}} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4944) Improve HR client security test coverage

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4944?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4944: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1167678|https://bugzilla.redhat.com/show_bug.cgi?id=1167678] from NEW to POST > Improve HR client security test coverage > ---------------------------------------- > > Key: ISPN-4944 > URL: https://issues.jboss.org/browse/ISPN-4944 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.1.0.Alpha1, 7.1.0.Final > > > Extends security test for HR client so that the tests cover all HR operations (available on [Remote cache|https://docs.jboss.org/infinispan/7.0/apidocs/org/infinispan/client...]) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5015) Update 2LC docu with CacheKey type support in clustered environments

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5015?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5015: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3103 > Update 2LC docu with CacheKey type support in clustered environments > -------------------------------------------------------------------- > > Key: ISPN-5015 > URL: https://issues.jboss.org/browse/ISPN-5015 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.Alpha1 > > > Depending on the cache key used, session factory name might have to be locked to a particular name across the cluster. All info available in the forum links. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4944) Improve HR client security test coverage

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4944?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4944: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1167678 > Improve HR client security test coverage > ---------------------------------------- > > Key: ISPN-4944 > URL: https://issues.jboss.org/browse/ISPN-4944 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.1.0.Alpha1, 7.1.0.Final > > > Extends security test for HR client so that the tests cover all HR operations (available on [Remote cache|https://docs.jboss.org/infinispan/7.0/apidocs/org/infinispan/client...]) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5015) Update 2LC docu with CacheKey type support in clustered environments

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5015?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5015: ----------------------------------- Status: Open (was: New) > Update 2LC docu with CacheKey type support in clustered environments > -------------------------------------------------------------------- > > Key: ISPN-5015 > URL: https://issues.jboss.org/browse/ISPN-5015 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.Alpha1 > > > Depending on the cache key used, session factory name might have to be locked to a particular name across the cluster. All info available in the forum links. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5015) Update 2LC docu with CacheKey type support in clustered environments

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5015?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5015: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > Update 2LC docu with CacheKey type support in clustered environments > -------------------------------------------------------------------- > > Key: ISPN-5015 > URL: https://issues.jboss.org/browse/ISPN-5015 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > > Depending on the cache key used, session factory name might have to be locked to a particular name across the cluster. All info available in the forum links. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5015) Update 2LC docu with CacheKey type support in clustered environments

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5015?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5015: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 > Update 2LC docu with CacheKey type support in clustered environments > -------------------------------------------------------------------- > > Key: ISPN-5015 > URL: https://issues.jboss.org/browse/ISPN-5015 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Fix For: 7.1.0.Alpha1 > > > Depending on the cache key used, session factory name might have to be locked to a particular name across the cluster. All info available in the forum links. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5015) Update 2LC docu with CacheKey type support in clustered environments

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5015?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-5015: -------------------------------------- Assignee: Galder Zamarreño > Update 2LC docu with CacheKey type support in clustered environments > -------------------------------------------------------------------- > > Key: ISPN-5015 > URL: https://issues.jboss.org/browse/ISPN-5015 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.Alpha1 > > > Depending on the cache key used, session factory name might have to be locked to a particular name across the cluster. All info available in the forum links. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2014