[JBoss JIRA] (ISPN-10937) CleanupAfterMethod tests take a very long time
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10937?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10937:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> CleanupAfterMethod tests take a very long time
> ----------------------------------------------
>
> Key: ISPN-10937
> URL: https://issues.jboss.org/browse/ISPN-10937
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.1.Final
> Reporter: dan.berindei
> Assignee: dan.berindei
> Priority: Major
> Fix For: 10.1.0.Beta1
>
>
> Because of JGRP-2398, every time the cluster is stopped and re-created the new coordinator first tries to connect to the old coordinator:
> {noformat}
> 13:53:39,024 DEBUG (testng-Test:[]) [GMS] address=Test-NodeA-57106, cluster=org.infinispan.partitionhandling.Test, physical address=127.0.0.1:55320
> 13:53:39,026 TRACE (testng-Test:[]) [GMS] Test-NodeA-57106: discovery took 0 ms, members: 17 rsps (4 coords) [done]
> 13:53:39,026 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: found multiple coords: [054b27e3-9308-65bf-de26-d6cdd4f6bdd3, 6d7f9fb2-f56b-1b88-7f9d-cdee430ac8ca, Test-NodeA-37104, Test-NodeA-8303]
> 13:53:39,026 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: sending JOIN(Test-NodeA-57106) to 6d7f9fb2-f56b-1b88-7f9d-cdee430ac8ca
> 13:53:41,026 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: JOIN(Test-NodeA-57106) sent to 6d7f9fb2-f56b-1b88-7f9d-cdee430ac8ca timed out (after 2000 ms), on try 0
> ...
> 13:53:45,027 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: sending JOIN(Test-NodeA-57106) to Test-NodeA-8303
> 13:53:47,027 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: JOIN(Test-NodeA-57106) sent to Test-NodeA-8303 timed out (after 2000 ms), on try 0
> ...
> 13:54:51,036 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: found multiple coords: [054b27e3-9308-65bf-de26-d6cdd4f6bdd3, 6d7f9fb2-f56b-1b88-7f9d-cdee430ac8ca, 0eb381de-3e9a-0320-b2d9-5db3cb39bb34, Test-NodeA-8303]
> 13:54:51,036 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: sending JOIN(Test-NodeA-57106) to 054b27e3-9308-65bf-de26-d6cdd4f6bdd3
> 13:54:53,036 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: JOIN(Test-NodeA-57106) sent to 054b27e3-9308-65bf-de26-d6cdd4f6bdd3 timed out (after 2000 ms), on try 9
> ...
> 13:54:57,037 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: sending JOIN(Test-NodeA-57106) to Test-NodeA-8303
> 13:54:59,037 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: JOIN(Test-NodeA-57106) sent to Test-NodeA-8303 timed out (after 2000 ms), on try 9
> 13:54:59,037 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: too many JOIN attempts (10): becoming singleton
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10922) StateTransferLinkFailuresTest random failures
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10922?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10922:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> StateTransferLinkFailuresTest random failures
> ---------------------------------------------
>
> Key: ISPN-10922
> URL: https://issues.jboss.org/browse/ISPN-10922
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.1.Final
> Reporter: dan.berindei
> Assignee: dan.berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.1.0.Beta1
>
>
> {{StateTransferLinkFailuresTest.testLinkBrokenDuringStateTransfer()}} tests that xsite state transfer eventually finishes when the link between sites is down. It simulates an exception in {{backupRemotely()}} and waits for 1 minute for state transfer to finish.
> The problem is that the default xsite state transfer retry configuration is to retry 30 times, waiting 2 seconds between retries. That means it's very possible the test will give up waiting on state transfer to finish just before state transfer finishes.
> {noformat}
> 21:43:02,524 DEBUG (transport-thread-Test-NodeA-p4484-t1:[]) [XSiteStateProviderImpl] [X-Site State Transfer - NYC-2] start DataContainer iteration
> 21:43:02,564 DEBUG (transport-thread-Test-NodeA-p4484-t1:[]) [XSiteStateProviderImpl] Sending chunk to site 'NYC-2'. Chunk contains [XSiteState{key=k_2, value=v_2, metadata=EmbeddedMetadata{version=null}}, XSiteState{key=k_4, value=v_4, metadata=EmbeddedMetadata{version=null}}]
> 21:44:02,579 TRACE (transport-thread-Test-NodeA-p4484-t1:[]) [RetryOnFailureXSiteCommand] Exception Response received. Exception is org.infinispan.util.concurrent.TimeoutException: induced timeout!
> 21:44:02,611 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.xsite.statetransfer.failures.StateTransferLinkFailuresTest.testLinkBrokenDuringStateTransfer[null, tx=false]
> java.lang.AssertionError:
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.14.3.jar:?]
> at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.14.3.jar:?]
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:250) ~[test-classes/:?]
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:232) ~[test-classes/:?]
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:208) ~[test-classes/:?]
> at org.infinispan.xsite.AbstractXSiteTest.assertEventuallyInSite(AbstractXSiteTest.java:193) ~[test-classes/:?]
> at org.infinispan.xsite.statetransfer.failures.StateTransferLinkFailuresTest.testLinkBrokenDuringStateTransfer(StateTransferLinkFailuresTest.java:89) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10924) JPA cache store (with async enabled) will log Exceptions in DEBUG for deleteBatch and is not able to remove entries from the store
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10924?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10924:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> JPA cache store (with async enabled) will log Exceptions in DEBUG for deleteBatch and is not able to remove entries from the store
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-10924
> URL: https://issues.jboss.org/browse/ISPN-10924
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.4.16.Final, 10.0.1.Final, 10.1.0.Beta1
> Environment: Embedded mode with configured ASYNC JPA CacheStore
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.17.Final, 10.1.0.Beta1, 10.0.2.Final
>
>
> If the cache is configured with a persistence of JPAStore in async mode each modification will log a DEBUG message like followed
> Oct 22, 2019 1:51:08 PM org.infinispan.persistence.async.AsyncCacheWriter$AsyncStoreProcessor retryWork
> DEBUG: Failed to process async modifications
> org.infinispan.persistence.jpa.JpaStoreException: Exception caught in deleteBatch()
> at org.infinispan.persistence.jpa.JpaStore.deleteBatch(JpaStore.java:357)
> at org.infinispan.persistence.async.AsyncCacheWriter.applyModificationsSync(AsyncCacheWriter.java:234)
> at org.infinispan.persistence.async.AsyncCacheWriter$AsyncStoreProcessor.retryWork(AsyncCacheWriter.java:463)
> at org.infinispan.persistence.async.AsyncCacheWriter$AsyncStoreProcessor.run(AsyncCacheWriter.java:423)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: Parameter value [org.infinispan.persistence.async.AsyncCacheWriter$$Lambda$136/1340865907@4c7c351c] did not match expected type [java.lang.String (n/a)]
> at org.hibernate.query.spi.QueryParameterBindingValidator.validate(QueryParameterBindingValidator.java:54)
> at org.hibernate.query.spi.QueryParameterBindingValidator.validate(QueryParameterBindingValidator.java:27)
> at org.hibernate.query.internal.QueryParameterBindingImpl.validate(QueryParameterBindingImpl.java:90)
> at org.hibernate.query.internal.QueryParameterBindingImpl.setBindValue(QueryParameterBindingImpl.java:55)
> at org.hibernate.query.internal.AbstractProducedQuery.setParameter(AbstractProducedQuery.java:493)
> at org.hibernate.query.internal.AbstractProducedQuery.setParameter(AbstractProducedQuery.java:106)
> at org.hibernate.query.criteria.internal.compile.CriteriaCompiler$1$1.bind(CriteriaCompiler.java:119)
> at org.hibernate.query.criteria.internal.AbstractManipulationCriteriaQuery$1.buildCompiledQuery(AbstractManipulationCriteriaQuery.java:135)
> at org.hibernate.query.criteria.internal.compile.CriteriaCompiler.compile(CriteriaCompiler.java:149)
> at org.hibernate.internal.SessionImpl.createQuery(SessionImpl.java:3724)
> at org.hibernate.internal.SessionImpl.createQuery(SessionImpl.java:207)
> at org.infinispan.persistence.jpa.JpaStore.deleteBatch(JpaStore.java:341)
> ... 6 more
> If entries should be removed this is only done in memory but the store will fail ASYNC.
> Because of the async contract there is only a warning wihtout any exact hint:
> WARN: ISPN000053: Unable to process some async modifications after 10 retries!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10906) JGroupsTransport instance is reused in tests
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10906?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10906:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> JGroupsTransport instance is reused in tests
> --------------------------------------------
>
> Key: ISPN-10906
> URL: https://issues.jboss.org/browse/ISPN-10906
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.1.Final
> Reporter: dan.berindei
> Assignee: dan.berindei
> Priority: Major
> Fix For: 10.1.0.CR1
>
>
> The {{TRANSPORT}} {{AttributeDefinition}} uses {{IdentityAttributeCopier}}, which means that when a test uses {{GlobalConfigurationBuilder.read()}} to make a clone of the global configuration it keeps using the same {{JGroupsTransport}} instance. Both cache managers sort of work, but usually not as intended.
> We should detect when {{JGroupsTransport}}'s dependencies are injected twice and throw an exception. We should also consider changing the {{TRANSPORT}} copier to {{SimpleInstanceAttributeCopier}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10911) HotRodMultiMapOperations random failures
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10911?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10911:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> HotRodMultiMapOperations random failures
> ----------------------------------------
>
> Key: ISPN-10911
> URL: https://issues.jboss.org/browse/ISPN-10911
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.1.Final
> Reporter: dan.berindei
> Assignee: dan.berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.1.0.Beta1
>
>
> Multimap operations are asynchronous, and the test doesn't wait for the writes to finish before starting a get. Multimap and Infinispan in general do not guarantee that asynchronous operations started from the same thread run in any particular order.
> {noformat}
> 09:07:49,325 ERROR (testng-HotRodMultiMapOperations:[]) [TestSuiteProgress] Test failed: HotRodMultiMapOperations.testMultiMap
> java.lang.AssertionError: expected:<2> but was:<0>
> at org.junit.Assert.fail(Assert.java:88) ~[junit-4.12.jar:4.12]
> at org.junit.Assert.failNotEquals(Assert.java:834) ~[junit-4.12.jar:4.12]
> at org.junit.Assert.assertEquals(Assert.java:645) ~[junit-4.12.jar:4.12]
> at org.junit.Assert.assertEquals(Assert.java:631) ~[junit-4.12.jar:4.12]
> at org.infinispan.server.functional.HotRodMultiMapOperations.testMultiMap(HotRodMultiMapOperations.java:41) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10881) Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10881?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10881:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains
> ----------------------------------------------------------------
>
> Key: ISPN-10881
> URL: https://issues.jboss.org/browse/ISPN-10881
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Core
> Affects Versions: 10.0.0.Final
> Reporter: dan.berindei
> Assignee: dan.berindei
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> {{allowDuplicateDomains}} is just a crutch for tests. Applications rarely start more than one cache manager in the same JVM, and when they (e.g. multiple applications in an application server) do it's always a good idea to give each cache manager a unique name.
> Our test suite doesn't really need {{allowDuplicateDomains}} either: {{TestCacheManagerFactory}} adds a UUID to the domain name, unless the test has explicitly set a (presumably unique) domain name.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10885) REST Reindex action
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10885?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10885:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> REST Reindex action
> -------------------
>
> Key: ISPN-10885
> URL: https://issues.jboss.org/browse/ISPN-10885
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Querying, REST
> Affects Versions: 10.0.1.Final
> Reporter: Tristan Tarrant
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> The Cache rest resource should implement a /rest/v2/caches/{cacheName}?action=reindex&mode=[sync|async]
> The method should return a 200 OK for sync and 202 Accepted for async reindex. It should also not initiate a new reindexing if one is running already and return 409 Conflict.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10888) Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10888?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10888:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided
> -------------------------------------------------------------------------------------------
>
> Key: ISPN-10888
> URL: https://issues.jboss.org/browse/ISPN-10888
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 10.0.0.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.1.0.Beta1
>
>
> Must avoid situations where ObjectName's type and component keys are equal, like in CacheManager_CacheManager_numberOfCreatedCaches. Same for Cache.
> In these cases do not add both, just one.
> Also, need to remove eventual dots from names. Replace them with the standard replacement character in MP metrics: ' _'
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10891) JGroupsTransport registers the channel in JMX ignoring the cacheManagerName
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10891?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10891:
-----------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36)
> JGroupsTransport registers the channel in JMX ignoring the cacheManagerName
> ---------------------------------------------------------------------------
>
> Key: ISPN-10891
> URL: https://issues.jboss.org/browse/ISPN-10891
> Project: Infinispan
> Issue Type: Bug
> Components: Core, JMX, reporting and management
> Affects Versions: 9.4.16.Final, 10.0.1.Final
> Reporter: dan.berindei
> Priority: Major
>
> {{JGroupsTransport}} registers the JGroups channel in JMX with a name like {{<jmx-domain>:type=channel,cluster={{cluster-name>}}.
> If two managers have a different {{cacheManagerName}}, all the cache manager and cache components can be registered along each other in the same JMX domain. The channel object name however doesn't include the manager name, so the 2nd cache manager fails to register its channel, and because of JGRP-2393 the cause of the error is hidden.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months