June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6224) Simplify configuration of Query with Indexing Affinity

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6224?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6224: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Simplify configuration of Query with Indexing Affinity > ------------------------------------------------------ > > Key: ISPN-6224 > URL: https://issues.jboss.org/browse/ISPN-6224 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Fix For: 9.4.0.Final > > > We should try to enable the "Index Affinity" capabilities in an easier way from a configuration point of view. > For example I wonder if the capabilities provided by the {{AffinityPartitioner}} could not be enabled by default, for example automatically decorating any user defined {{HashFunctionPartitioner}} so that people can't neither forget to enable it, nor override it. > Second, should it be enabled by default when the cache configuration suggests it, for example in most clustered caches? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6220) Speedup index rebuilds but using ADD rather than UPDATE statements when safe

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6220?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6220: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Speedup index rebuilds but using ADD rather than UPDATE statements when safe > ---------------------------------------------------------------------------- > > Key: ISPN-6220 > URL: https://issues.jboss.org/browse/ISPN-6220 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Fix For: 9.4.0.Final > > > The {{DistributedExecutorMassIndexer}} relies on update commands to index the new entries, but when we just run a full purge of the index it should be safe to use Add commands instead if we know that there aren't concurrent updates. > The lack of concurrent updates might be tricky but I think we can find such a condition when using Affinity as the index is being fully controlled by the current indexing engine, similarly to the checks to see if it's safe to use an NRT workspace. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6809) Monitor indexing status

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6809?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6809: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Monitor indexing status > ----------------------- > > Key: ISPN-6809 > URL: https://issues.jboss.org/browse/ISPN-6809 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > Fix For: 9.4.0.Final > > > Status of mass indexer and index status should be displayed per cache. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6639) Implement multi-tenancy for Memcached

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6639?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6639: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Implement multi-tenancy for Memcached > ------------------------------------- > > Key: ISPN-6639 > URL: https://issues.jboss.org/browse/ISPN-6639 > Project: Infinispan > Issue Type: Sub-task > Components: Memcached, Server > Reporter: Sebastian Łaskawiec > Priority: Optional > Fix For: 9.4.0.Final > > > Currently this implementation is out of scope. Please vote for it if you'd like it to be implemented. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6638) Implement multi-tenancy for Web Sockets

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6638?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6638: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Implement multi-tenancy for Web Sockets > --------------------------------------- > > Key: ISPN-6638 > URL: https://issues.jboss.org/browse/ISPN-6638 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Priority: Optional > Fix For: 9.4.0.Final > > > Currently this implementation is out of scope. Please vote for it if you'd like it to be implemented. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6635) Multi tenancy

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6635?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6635: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Multi tenancy > ------------- > > Key: ISPN-6635 > URL: https://issues.jboss.org/browse/ISPN-6635 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 9.4.0.Final > > > Hosting Infinispan as a Service requires support of multi tenancy. > The design for this feature might be found here: https://github.com/infinispan/infinispan/wiki/Multi-tenancy-for-Hotrod-Se... > And implementation plan in the subtasks. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6585) Persistence support in functional API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6585?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6585: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Persistence support in functional API > ------------------------------------- > > Key: ISPN-6585 > URL: https://issues.jboss.org/browse/ISPN-6585 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6479) CacheRpcCommandExternalizer should cache the cache name bytes

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6479?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6479: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > CacheRpcCommandExternalizer should cache the cache name bytes > ------------------------------------------------------------- > > Key: ISPN-6479 > URL: https://issues.jboss.org/browse/ISPN-6479 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6477) Security tests always log a warning during cache manager shutdown

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6477?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6477: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Security tests always log a warning during cache manager shutdown > ----------------------------------------------------------------- > > Key: ISPN-6477 > URL: https://issues.jboss.org/browse/ISPN-6477 > Project: Infinispan > Issue Type: Bug > Components: Security, Test Suite - Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha1, 9.4.0.Final > > > The problem is that {{TestingUtil.killCacheManagers()}} first stops each cache explicitly, and then {{DefaultCacheManager.stop()}} fails because it can't access the global ACL cache to perform a security check: > {noformat} > 17:07:00,613 WARN (testng-ExecutionAuthorizationTest:[]) [TestingUtil] Problems killing cache manager org.infinispan.manager.DefaultCacheManager@4e83a98@Address:ExecutionAuthorizationTest-NodeB-14717 > org.infinispan.IllegalLifecycleStateException: ISPN000323: ___acl_cache is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.cache.impl.SimpleCacheImpl.getDataContainer(SimpleCacheImpl.java:1044) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsentInternal(SimpleCacheImpl.java:1116) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.StatsCollectingCache.computeIfAbsentInternal(StatsCollectingCache.java:270) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsent(SimpleCacheImpl.java:1111) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkSubjectPermissionAndRole(AuthorizationHelper.java:107) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:76) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:42) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.SecureCacheImpl.getComponentRegistry(SecureCacheImpl.java:336) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.unregisterCacheMBean(DefaultCacheManager.java:714) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:671) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:708) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:688) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:673) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:656) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:652) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.MultipleCacheManagersTest.destroy(MultipleCacheManagersTest.java:87) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > {noformat} > {{DefaultCacheManager.stop()}} could check a cache's status before trying to unregister it from JMX, avoiding the security check when the cache is already {{TERMINATED}}. > {{DefaultCacheManager.unregisterCacheMBean()}} could also extract the cache's component registry from the global component registry and avoid the security check, since {{DefaultCacheManager.stop()}} already performed a security check. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6476) Integration test modules shouldn't change the failsafe plugin's lifecycle

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6476?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6476: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Integration test modules shouldn't change the failsafe plugin's lifecycle > ------------------------------------------------------------------------- > > Key: ISPN-6476 > URL: https://issues.jboss.org/browse/ISPN-6476 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Fix For: 9.4.0.Final > > > Many of our integration tests modules run the {{integration-test}} and {{verify}} goals of {{maven-failsafe-plugin}} together, sometimes specifying a lifecycle phase, sometimes not. This shouldn't be necessary, because failsafe runs both goals, it just binds them to different phases. > On the contrary, running both goals in the same phase can fail the build too early, skipping any executions bound to the {{post-integration-test}} phase. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 June 2018