January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6105) Too many warnings logged for total order commands

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6105?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6105: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3955 > Too many warnings logged for total order commands > ------------------------------------------------- > > Key: ISPN-6105 > URL: https://issues.jboss.org/browse/ISPN-6105 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Beta1 > > > {{RetryPrepareException}} is harmless, on the same level as {{OutdatedTopologyException}}, so it should be logged at debug level instead of warning. > Tx commands received before the initial topology also result in a {{NullPointerException}} that is logged at the error level, because they try to access the transaction table before it finished initializing. Non-TO tx commands avoid this by calling {{isCommandSentBeforeFirstTopology(commandTopologyId)}}, TO tx commands can do the same. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6105) Too many warnings logged for total order commands

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6105?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6105: ------------------------------- Status: Open (was: New) > Too many warnings logged for total order commands > ------------------------------------------------- > > Key: ISPN-6105 > URL: https://issues.jboss.org/browse/ISPN-6105 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Beta1 > > > {{RetryPrepareException}} is harmless, on the same level as {{OutdatedTopologyException}}, so it should be logged at debug level instead of warning. > Tx commands received before the initial topology also result in a {{NullPointerException}} that is logged at the error level, because they try to access the transaction table before it finished initializing. Non-TO tx commands avoid this by calling {{isCommandSentBeforeFirstTopology(commandTopologyId)}}, TO tx commands can do the same. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6105) Too many warnings logged for total order commands

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6105: ---------------------------------- Summary: Too many warnings logged for total order commands Key: ISPN-6105 URL: https://issues.jboss.org/browse/ISPN-6105 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 8.1.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.2.0.Beta1 {{RetryPrepareException}} is harmless, on the same level as {{OutdatedTopologyException}}, so it should be logged at debug level instead of warning. Tx commands received before the initial topology also result in a {{NullPointerException}} that is logged at the error level, because they try to access the transaction table before it finished initializing. Non-TO tx commands avoid this by calling {{isCommandSentBeforeFirstTopology(commandTopologyId)}}, TO tx commands can do the same. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6104) Cache.Purge issues

by Martin Gencur (JIRA)

Martin Gencur created ISPN-6104: ----------------------------------- Summary: Cache.Purge issues Key: ISPN-6104 URL: https://issues.jboss.org/browse/ISPN-6104 Project: Infinispan Issue Type: Bug Components: Console Reporter: Martin Gencur Assignee: Vladimir Blagojevic Currently, there are the following issues with the "Purge cache data" button: 1) The button is available even though the cache is attached to the remote endpoint and hence available to clients. It should only be available after the cache is detached from the endpoint. 2) The confirmation dialog for the operation always says "Purging cache xyCache will passivate all its cache entries." even though there's no cache store defined for the cache. This might lead users to expectations that their data will be stored somewhere. But if there's no cache store, the data will be lost. In this case, it would be better to show a warning that their data will be lost after performing the operation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6100) L1 entries not always stored as L1InternalCacheEntry

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6100?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6100: ------------------------------- Labels: testsuite_stability (was: testsuite_failure) > L1 entries not always stored as L1InternalCacheEntry > ---------------------------------------------------- > > Key: ISPN-6100 > URL: https://issues.jboss.org/browse/ISPN-6100 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 8.2.0.Beta1 > > > {{DistributedClusteringLogic.commitSingleEntry}} is using regular {{Metadata}} instead of {{L1Metadata}} when storing entries that are not owned by the local node. The entry will then be stored as a regular {{MortalCacheEntry}} instead of an {{L1InternalCacheEntry}}. > In non-transactional mode, I believe this can only happen if the node was an owner at the time of entry wrapping. I'm not sure if the same applies in transactional caches. > {{BaseDistFunctionalTest.assertOwnershipAndNonOwnership()}} assumes L1 entries are stored as {{L1InternalCacheEntries}}, so at the very least the mismatch results in random test failures in {{BaseDistFunctionalTest}} subclasses like {{ConcurrentJoinTest}}. It may result in stale data as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6103) LocalKeyAffinityTest.testFilteredRemoveServers random failures

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6103: ---------------------------------- Summary: LocalKeyAffinityTest.testFilteredRemoveServers random failures Key: ISPN-6103 URL: https://issues.jboss.org/browse/ISPN-6103 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Affects Versions: 8.1.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.2.0.Beta1 {noformat} 19:04:00,884 ERROR (testng-LocalKeyAffinityServiceTest:) [UnitTestTestNGListener] Test testFilteredRemoveServers(org.infinispan.affinity.impl.LocalKeyAffinityServiceTest) failed. java.lang.AssertionError: at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.8.8.jar:?] at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.8.8.jar:?] at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:109) ~[test-classes/:?] at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:91) ~[test-classes/:?] at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:67) ~[test-classes/:?] at org.infinispan.affinity.impl.BaseKeyAffinityServiceTest.assertEventualFullCapacity(BaseKeyAffinityServiceTest.java:77) ~[test-classes/:?] at org.infinispan.affinity.impl.BaseFilterKeyAffinityServiceTest.assertUnaffected(BaseFilterKeyAffinityServiceTest.java:86) ~[test-classes/:?] at org.infinispan.affinity.impl.BaseFilterKeyAffinityServiceTest.testRemoveServers(BaseFilterKeyAffinityServiceTest.java:60) ~[test-classes/:?] at org.infinispan.affinity.impl.LocalKeyAffinityServiceTest.testFilteredRemoveServers(LocalKeyAffinityServiceTest.java:47) ~[test-classes/:?] {noformat} Counting the number of generated keys in the log, it seems to be correct, need better logging to determine if there are too few or too many keys in the queue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6102) Include the test name in the test thread names

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6102: ---------------------------------- Summary: Include the test name in the test thread names Key: ISPN-6102 URL: https://issues.jboss.org/browse/ISPN-6102 Project: Infinispan Issue Type: Task Components: Test Suite - Core Affects Versions: 8.1.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.2.0.Beta1 Some random failures are much easier to reproduce when running the entire core test suite, which runs 15 tests in paralle, than when running a single test by itself. In such cases, it helps if we can filter the log messages that belong to the failing test, and the easiest way to do that is to include the test name in the thread name. Essentially, this means replacing {{ExecutorService}} instances with {{AbstractInfinispanTest.fork()}}, and where not possible instantiating the executor with {{AbstractInfinispanTest.getTestThreadFactory()}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6101) Deprecate M/R and point to Distributed Streams

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6101?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6101: -------------------------------- Status: Open (was: New) > Deprecate M/R and point to Distributed Streams > ---------------------------------------------- > > Key: ISPN-6101 > URL: https://issues.jboss.org/browse/ISPN-6101 > Project: Infinispan > Issue Type: Task > Reporter: William Burns > Assignee: William Burns > Fix For: 8.2.0.CR1 > > > Map Reduce will be removed for ISPN 9. We need to make sure it is deprecated in a version before to let user base know. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6101) Deprecate M/R and point to Distributed Streams

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6101?page=com.atlassian.jira.plugin.... ] Work on ISPN-6101 started by William Burns. ------------------------------------------- > Deprecate M/R and point to Distributed Streams > ---------------------------------------------- > > Key: ISPN-6101 > URL: https://issues.jboss.org/browse/ISPN-6101 > Project: Infinispan > Issue Type: Task > Reporter: William Burns > Assignee: William Burns > Fix For: 8.2.0.CR1 > > > Map Reduce will be removed for ISPN 9. We need to make sure it is deprecated in a version before to let user base know. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6101) Deprecate M/R and point to Distributed Streams

by William Burns (JIRA)

William Burns created ISPN-6101: ----------------------------------- Summary: Deprecate M/R and point to Distributed Streams Key: ISPN-6101 URL: https://issues.jboss.org/browse/ISPN-6101 Project: Infinispan Issue Type: Task Reporter: William Burns Assignee: William Burns Fix For: 8.2.0.CR1 Map Reduce will be removed for ISPN 9. We need to make sure it is deprecated in a version before to let user base know. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016