November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-7035) Move spring modules to proper packages

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7035?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7035: ---------------------------------- Sprint: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha0 (was: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha0) > Move spring modules to proper packages > -------------------------------------- > > Key: ISPN-7035 > URL: https://issues.jboss.org/browse/ISPN-7035 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Katia Aresti > Priority: Critical > Fix For: 10.0.0.Final > > > Currently everything is placed in {{org.infinispan.spring}} package. We should provide exactly the same split as we did in CDI ({{org.infinispan.spring}} into {{org.infinispan.spring.remote}} and {{org.infinispan.spring.embedded}}) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding for C++

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9036?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9036: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0 (was: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0) > Parameterized branding for C++ > ------------------------------ > > Key: ISPN-9036 > URL: https://issues.jboss.org/browse/ISPN-9036 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9382) Jenkins release pipeline should handle multiple branches and reversioning

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9382?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9382: ---------------------------------- Sprint: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0 (was: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0) > Jenkins release pipeline should handle multiple branches and reversioning > ------------------------------------------------------------------------- > > Key: ISPN-9382 > URL: https://issues.jboss.org/browse/ISPN-9382 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.2.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9564) Align pom.xml order and versions

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9564?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9564: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0 (was: Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0) > Align pom.xml order and versions > -------------------------------- > > Key: ISPN-9564 > URL: https://issues.jboss.org/browse/ISPN-9564 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.2.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9668) Document accessing Infinispan cache metrics via Spring Actuator

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9668?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9668: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha0 (was: Sprint 10.0.0.Alpha0) > Document accessing Infinispan cache metrics via Spring Actuator > --------------------------------------------------------------- > > Key: ISPN-9668 > URL: https://issues.jboss.org/browse/ISPN-9668 > Project: Infinispan > Issue Type: Feature Request > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Spring-Actuator statistics in embedded mode are not either integrated, either documented on how to display them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8616) DistAsyncFuncTest.testMergeFromNonOwner random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8616?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8616: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha0 (was: Sprint 10.0.0.Alpha0) > DistAsyncFuncTest.testMergeFromNonOwner random failures > ------------------------------------------------------- > > Key: ISPN-8616 > URL: https://issues.jboss.org/browse/ISPN-8616 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Alpha1 > > > {noformat} > java.lang.AssertionError: Fail on owner cache DistAsyncFuncTest[DIST_ASYNC, tx=false]-NodeA-42474: dc.get(k1) returned null > at org.infinispan.distribution.BaseDistFunctionalTest.assertOwnershipAndNonOwnership(BaseDistFunctionalTest.java:191) > at org.infinispan.distribution.BaseDistFunctionalTest.assertOnAllCachesAndOwnership(BaseDistFunctionalTest.java:162) > at org.infinispan.distribution.BaseDistFunctionalTest.initAndTest(BaseDistFunctionalTest.java:142) > at org.infinispan.distribution.DistSyncFuncTest.testMergeFromNonOwner(DistSyncFuncTest.java:387) > {noformat} > The test method is new and the interceptors have changed, but it's probably the same problem with {{asyncWait}} signaled in ISPN-3741. I commented out the entire implementation of {{asyncWait}} in {{DistAsyncFuncTest}} and it still passed when run by itself, so we need a way to delay the commands and check that the test is not sensitive to such delays. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9366) Cache.size optimizations

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9366?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9366: ---------------------------------- Sprint: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0 (was: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0) > Cache.size optimizations > ------------------------ > > Key: ISPN-9366 > URL: https://issues.jboss.org/browse/ISPN-9366 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.2.Final > > > Now that we have a segmented data container and segmented store we can add optimizations for the Cache.size operation in various configurations. > If a store is configured, passivation must be disabled for any of these optimizations related to stores to work > # Shared store can just invoke Store.size > # No store & no expired entries can invoke DataContainer.sizeIncludingExpired(IntSet) > # Non shared store can invoke Store.size(IntSet) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8861) DIST Iteration shouldn't go remote when a shared cache store is present

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8861?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8861: ---------------------------------- Sprint: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0 (was: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0) > DIST Iteration shouldn't go remote when a shared cache store is present > ----------------------------------------------------------------------- > > Key: ISPN-8861 > URL: https://issues.jboss.org/browse/ISPN-8861 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.2.Final > > > When a user runs a distributed iteration operation with a shared cache store, this shouldn't go remote as the local node would have all the data available to it. This is similar to the optimization when we don't go remote if the current node is an owner for all required segments. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5997) JMX operation ClusterCacheStats.resetStatistics() not working

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5997?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5997: ---------------------------------- Sprint: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0 (was: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0) > JMX operation ClusterCacheStats.resetStatistics() not working > ------------------------------------------------------------- > > Key: ISPN-5997 > URL: https://issues.jboss.org/browse/ISPN-5997 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.1.0.CR1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Major > > Environment: 2 servers started in domain mode (ISPN 8.1.0.CR1). > Having some clustered cache, inserted/read some entries (just to create some statistics). > When connected via JMX (e.g. through JConsole, see https://issues.jboss.org/browse/ISPN-5983 ) to one of the servers, I execute resetStatistics() operation on ClusterCacheStats MBean (object name: jboss.datagrid-infinispan:type=Cache,name="<cache-name>",manager="<cache-container-name>",component=ClusterCacheStats) and nothing happens, the cluster statistics are not reset. > To actually reset the statistics, I have to connect to each of the servers in domain individually and call resetStatistics() on Statistics MBean, which deletes "a portion" of statistics of that particular server to the cluster stats. > I would expect ClusterCacheStats.resetStatistics() to do exactly the same: call Statistics.resetStatistics() on each server. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9257) ClustertopologyManagerTest.testAbruptLeaveAfterGetStatus2[SCATTERED_SYNC, tx=false] random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9257?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9257: ---------------------------------- Sprint: Sprint 9.3.0.Final, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0 (was: Sprint 9.3.0.Final, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0) > ClustertopologyManagerTest.testAbruptLeaveAfterGetStatus2[SCATTERED_SYNC, tx=false] random failures > --------------------------------------------------------------------------------------------------- > > Key: ISPN-9257 > URL: https://issues.jboss.org/browse/ISPN-9257 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.3.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 9.4.2.Final > > Attachments: ISPN-8731_wrong_topology_2018-05-18_ClusterTopologyManagerTest-infinispan-core.log.gz > > > The test kills the coordinator NodeA, then while NodeB is trying to recover the caches it also kills NodeC. It expects NodeB to start a rebalance with 2 nodes and discards it, in order to test that it can process the 1-node rebalance first: > {noformat} > 00:34:06,582 DEBUG (transport-thread-test-NodeB-p12-t6:[testCache]) [ClusterTopologyManagerTest] Discarding rebalance command CacheTopology{id=8, phase=TRANSITORY, rebalanceId=5, currentCH=ScatteredConsistentHash{ns=256, rebalanced=false, owners = (2)[test-NodeB-49590: 85, test-NodeC-58596: 85]}, pendingCH=ScatteredConsistentHash{ns=256, rebalanced=true, owners = (2)[test-NodeB-49590: 128, test-NodeC-58596: 128]}, unionCH=null, actualMembers=[test-NodeB-49590, test-NodeC-58596], persistentUUIDs=[6b96414e-15d8-4350-aa3c-4fb4fc34e888, d47dc4a9-2a95-4bb1-a83b-bb8a27c9999f]} > 00:34:06,609 DEBUG (transport-thread-test-NodeB-p12-t2:[Topology-testCache]) [LocalTopologyManagerImpl] Updating local topology for cache testCache: CacheTopology{id=9, phase=TRANSITORY, rebalanceId=5, currentCH=ScatteredConsistentHash{ns=256, rebalanced=false, owners = (1)[test-NodeB-49590: 85]}, pendingCH=ScatteredConsistentHash{ns=256, rebalanced=false, owners = (1)[test-NodeB-49590: 128]}, unionCH=null, actualMembers=[test-NodeB-49590], persistentUUIDs=[6b96414e-15d8-4350-aa3c-4fb4fc34e888]} > 00:34:06,609 DEBUG (transport-thread-test-NodeB-p12-t2:[Topology-testCache]) [LocalTopologyManagerImpl] Installing fake cache topology CacheTopology{id=8, phase=NO_REBALANCE, rebalanceId=4, currentCH=ScatteredConsistentHash{ns=256, rebalanced=false, owners = (1)[test-NodeB-49590: 85]}, pendingCH=null, unionCH=null, actualMembers=[test-NodeB-49590], persistentUUIDs=[6b96414e-15d8-4350-aa3c-4fb4fc34e888]} for cache testCache > {noformat} > Unfortunately {{PreferAvailabilityStrategy}} has changed a bit and the rebalance ids don't always match the expectations of the test, so that the 1-node rebalance is discarded instead: > {noformat} > 09:46:10,530 DEBUG (transport-thread-Test-NodeB-p54539-t3:[testCache]) [Test] Discarding rebalance command CacheTopology{id=9, phase=TRANSITORY, rebalanceId=5, currentCH=ScatteredConsistentHash{ns=256, rebalanced=false, owners = (1)[Test-NodeB-62039: 85]}, pendingCH=ScatteredConsistentHash{ns=256, rebalanced=true, owners = (1)[Test-NodeB-62039: 256]}, unionCH=null, actualMembers=[Test-NodeB-62039], persistentUUIDs=[0ed7be74-4485-489b-baee-28c461c9e5de]} > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2018