June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9190) Make trace logging faster by writing a separate log file for each test

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9190?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9190: ------------------------------------- Fix Version/s: 9.3.0.Final (was: 9.3.0.CR1) > Make trace logging faster by writing a separate log file for each test > ---------------------------------------------------------------------- > > Key: ISPN-9190 > URL: https://issues.jboss.org/browse/ISPN-9190 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Final > > > Logging each test to a separate file is cheaper because each test uses a separate appender, so there's no contention. The total size may also be smaller (with {{CompressedFileAppender}}) because the test name is repeated a lot and there isn't so much overlap between different tests. > Most important, keeping only the logs of failed tests becomes much faster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9191) ExceptionEvictionTest random failure during clearContent

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9191?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9191: ------------------------------------- Fix Version/s: 9.3.0.Final (was: 9.3.0.CR1) > ExceptionEvictionTest random failure during clearContent > -------------------------------------------------------- > > Key: ISPN-9191 > URL: https://issues.jboss.org/browse/ISPN-9191 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Final > > > There is a random failure that occurs for ExceptionEvictionTest. > After each test is run we verify that there are no pending transactions leftover. It seems that the cause is due to the tx completion is sent asynchronously that we need to wait for them to clean up to verify. > This is related to https://issues.jboss.org/browse/ISPN-9189 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9194) EntityRegionAccessStrategyTest.testRemoveAll failing randomly

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9194?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9194: ------------------------------------- Fix Version/s: (was: 9.3.0.CR1) > EntityRegionAccessStrategyTest.testRemoveAll failing randomly > ------------------------------------------------------------- > > Key: ISPN-9194 > URL: https://issues.jboss.org/browse/ISPN-9194 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.Final > > Attachments: ispn9194-log-v3.tgz, ispn9194-log-v4.tgz > > > {code} > [INFO] Running org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest > [ERROR] Tests run: 153, Failures: 1, Errors: 0, Skipped: 17, Time elapsed: 23.447 s <<< FAILURE! - in org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest > [ERROR] testRemoveAll[JTA, REPL_SYNC, AccessType[read-only]](org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest) Time elapsed: 0.01 s <<< FAILURE! > java.lang.AssertionError: expected:<VALUE1/1> but was:<null> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.infinispan.test.hibernate.cache.commons.AbstractRegionAccessStrategyTest.evictOrRemoveAllTest(AbstractRegionAccessStrategyTest.java:490) > at org.infinispan.test.hibernate.cache.commons.AbstractRegionAccessStrategyTest.testRemoveAll(AbstractRegionAccessStrategyTest.java:433) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9186) Upgrade Protostream to 4.3.0.Alpha1

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9186?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9186: ------------------------------------- Fix Version/s: 9.3.0.Final (was: 9.3.0.CR1) > Upgrade Protostream to 4.3.0.Alpha1 > ----------------------------------- > > Key: ISPN-9186 > URL: https://issues.jboss.org/browse/ISPN-9186 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9187) Lost segments logged when node leaves during rebalance

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9187?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9187: ------------------------------------- Fix Version/s: 9.3.0.Final (was: 9.3.0.CR1) > Lost segments logged when node leaves during rebalance > ------------------------------------------------------ > > Key: ISPN-9187 > URL: https://issues.jboss.org/browse/ISPN-9187 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.3.Final, 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > > When a node leaves during rebalance, we remove the leaver from the current CH and from the pending CH with {{ConsistentHashFactory.updateMembers()}}. However, since the 4-phase rebalance changes joiners are also removed from the pending CH. > In the following log numOwners=2 and pending CH had one segment (239) owned by a joiner (D) and a leaver (B). The updated pending CH doesn't have either B or D, this means both owners are lost and random owners (C and A) are elected. A sees that it was allocated new segments from {{updateMembers}} and logs that the segment has been lost: > {noformat} > 08:53:01,528 INFO (remote-thread-test-NodeA-p2-t6:[cluster-listener]) [CLUSTER] [Context=cluster-listener] ISPN100002: Starting rebalance with members [test-NodeA-15001, test-NodeB-55628, test-NodeC-62395, test-NodeD-29215], phase READ_OLD_WRITE_ALL, topology id 10 > 08:53:01,554 TRACE (transport-thread-test-NodeD-p28-t2:[Topology-cluster-listener]) [CacheTopology] Current consistent hash's routing table: test-NodeA-15001 primary: {... 237-238 244-245 248-250 252 254}, backup: {... 235-236 243 246-247 251 253} > test-NodeB-55628 primary: {... 231 234 240 242}, backup: {... 232-233 239 241 255} > test-NodeC-62395 primary: {... 232-233 235-236 239 241 243 246-247 251 253 255}, backup: {... 231 234 237-238 240 242 244-245 248-250 252 254} > 08:53:01,554 TRACE (transport-thread-test-NodeD-p28-t2:[Topology-cluster-listener]) [CacheTopology] Pending consistent hash's routing table: test-NodeA-15001 primary: {... 237-238 245 248 252}, backup: {... 235-236 244 246-247 251} > test-NodeB-55628 primary: {... 231 240 242}, backup: {... 230 239 241} > test-NodeC-62395 primary: {... 232-233 235-236 241 243 246-247 251 253 255}, backup: {... 231 234 240 242 245 249-250 252 254} > test-NodeD-29215 primary: {... 234 239 244 249-250 254}, backup: {... 232-233 237-238 243 248 253 255} > 08:53:01,606 TRACE (remote-thread-test-NodeA-p2-t5:[cluster-listener]) [ClusterCacheStatus] Removed node test-NodeB-55628 from cache cluster-listener: members = [test-NodeA-15001, test-NodeC-62395, test-NodeD-29215], joiners = [test-NodeD-29215] > 08:53:01,611 TRACE (remote-thread-test-NodeA-p2-t5:[cluster-listener]) [CacheTopology] Current consistent hash's routing table: test-NodeA-15001 primary: {... 237-238 244-245 248-250 252 254}, backup: {... 235-236 243 246-247 251 253} > test-NodeC-62395 primary: {... 230-236 239-243 246-247 251 253 255}, backup: {... 237-238 244-245 248-250 252 254} > 08:53:01,611 TRACE (remote-thread-test-NodeA-p2-t5:[cluster-listener]) [CacheTopology] Pending consistent hash's routing table: test-NodeA-15001 primary: {... 237-238 244-245 248 252}, backup: {... 235-236 239 246-247 251} > test-NodeC-62395 primary: {... 227-236 239-243 246-247 249-251 253-255}, backup: {... 226 245 252} > 08:53:01,613 TRACE (transport-thread-test-NodeA-p4-t1:[Topology-cluster-listener]) [StateTransferManagerImpl] Installing new cache topology CacheTopology{id=11, phase=READ_OLD_WRITE_ALL, rebalanceId=4, currentCH=DefaultConsistentHash{ns=256, owners = (2)[test-NodeA-15001: 134+45, test-NodeC-62395: 122+50]}, pendingCH=DefaultConsistentHash{ns=256, owners = (2)[test-NodeA-15001: 129+45, test-NodeC-62395: 127+28]}, unionCH=DefaultConsistentHash{ns=256, owners = (2)[test-NodeA-15001: 134+62, test-NodeC-62395: 122+68]}, actualMembers=[test-NodeA-15001, test-NodeC-62395, test-NodeD-29215], persistentUUIDs=[0506cc27-9762-4703-ad56-6a3bf7953529, c365b93f-e46c-4f11-ab46-6cafa2b2d92b, d3f21b0d-07f2-4089-b160-f754e719de83]} on cache cluster-listener > 08:53:01,662 TRACE (transport-thread-test-NodeA-p4-t1:[Topology-cluster-listener]) [StateConsumerImpl] On cache cluster-listener we have: new segments: {1-18 21 30-53 56-63 67 69-73 75-78 81-85 88-101 107-115 117-118 125-134 136-139 142-156 158-165 168-170 172-174 177-179 181-188 193-211 214-226 228-229 235-239 243-254}; old segments: {1-15 30-53 56-63 69-73 75-77 81-85 88-101 107-115 117-118 125-131 136-139 142-145 150-156 158-165 168-170 172-174 177-179 183-188 193-211 214-218 220-226 228-229 235-238 243-254} > 08:53:01,663 TRACE (transport-thread-test-NodeA-p4-t1:[Topology-cluster-listener]) [StateConsumerImpl] On cache cluster-listener we have: added segments: {16-18 21 67 78 132-134 146-149 181-182 219 239}; removed segments: {} > 08:53:01,663 DEBUG (transport-thread-test-NodeA-p4-t1:[Topology-cluster-listener]) [StateConsumerImpl] Not requesting segments {16-18 21 67 78 132-134 146-149 181-182 219 239} because the last owner left the cluster > {noformat} > There isn't any visible inconsistency: A only owns segment 239 for writing, and the coordinator immediately starts a new rebalance, ignoring the pending CH that it sent out earlier. However, the new rebalance causes its own problems: ISPN-8240. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9252) Easier statistics collection in NettyTransportConnectionStats

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9252?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9252: ------------------------------------- Fix Version/s: 9.3.0.Final (was: 9.3.0.CR1) > Easier statistics collection in NettyTransportConnectionStats > -------------------------------------------------------------- > > Key: ISPN-9252 > URL: https://issues.jboss.org/browse/ISPN-9252 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Galder Zamarreño > Fix For: 9.3.0.Final > > > NettyTransportConnectionStats should have an easier way to get statistics rather than going over JMX itself. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9254) Document Single Port

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9254?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9254: ------------------------------------- Fix Version/s: (was: 9.3.0.CR1) > Document Single Port > -------------------- > > Key: ISPN-9254 > URL: https://issues.jboss.org/browse/ISPN-9254 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Sebastian Łaskawiec > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9246) DataContainer should be in a public package

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9246?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9246: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > DataContainer should be in a public package > ------------------------------------------- > > Key: ISPN-9246 > URL: https://issues.jboss.org/browse/ISPN-9246 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.CR1 > > > The DataContainer interface should be in a public package. We need to move all the other classes into an impl package instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9212) Bypass interceptors for nontx REPL reads

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9212?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9212: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Bypass interceptors for nontx REPL reads > ---------------------------------------- > > Key: ISPN-9212 > URL: https://issues.jboss.org/browse/ISPN-9212 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.3.0.Beta1 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.CR1 > > > It should be possible to completely bypass the interceptor stack and directly query the data container with a REPL cache. We just can only do this when it is non tx, has no persistence. We would have to do stats and notifications manually. > It could even be possible to add this to all cache modes and fall back to the interceptor stack if no entry was found. This would slow down the miss state minimally, however the hot path would be increased. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9245) ReflectionUtil.getAllMethods misses interfaces extended by another interface

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9245?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9245: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ReflectionUtil.getAllMethods misses interfaces extended by another interface > ---------------------------------------------------------------------------- > > Key: ISPN-9245 > URL: https://issues.jboss.org/browse/ISPN-9245 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.3.0.Beta1 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.CR1 > > > ReflectionUtil.getAllMethods that returns all methods that have a given annotation on it will not return methods from an interface that was extended another and the implementing class doesn't define the super interface. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018