January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5476) Cross-site tests should run in parallel

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5476?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5476: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Cross-site tests should run in parallel > --------------------------------------- > > Key: ISPN-5476 > URL: https://issues.jboss.org/browse/ISPN-5476 > Project: Infinispan > Issue Type: Task > Components: Core, Cross-Site Replication, Test Suite - Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Fix For: 8.2.0.CR1 > > > Currently the cross-site tests have to run in a single thread, and that means they're much slower than the regular core tests. > It also means they need to run with a separate Maven profile, and that (combined with their duration) makes it very unlikely for devs to run the xsite tests on their machines. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5469) Remote-executor threads should not block during RPCs

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5469?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5469: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Remote-executor threads should not block during RPCs > ---------------------------------------------------- > > Key: ISPN-5469 > URL: https://issues.jboss.org/browse/ISPN-5469 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Fix For: 8.2.0.CR1 > > > This is particularly important in non-transactional caches, where the primary owner has to forward a command to the backup owners. The remote-executor thread on the primary should not be blocked while waiting for the backup responses, and instead process other commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5513) State Transfer can miss entries that are concurrently activated

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5513?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5513: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > State Transfer can miss entries that are concurrently activated > --------------------------------------------------------------- > > Key: ISPN-5513 > URL: https://issues.jboss.org/browse/ISPN-5513 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 8.0.0.Alpha1 > Reporter: William Burns > Fix For: 8.2.0.CR1 > > > Currently the OutboundTransferTask iterates upon the data container and then runs process for the state loader. However if an entry is activated during or after the data container iteration it is possible this entry is then not seen and subsequently is not present in the store when it is processed. > EntryRetriever had this same issue and it was required to register a cache listener to listen for activations and then replay the data after finishing with the store. > This can cause duplicate values as well, however replacing the same exact value is fine and if a non ST write occurs the state is ignored anyways. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5506) Dist/ReplEmbeddedRestHotRodTest failing randomly with "java.net.SocketException: Socket closed"

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5506?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5506: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Dist/ReplEmbeddedRestHotRodTest failing randomly with "java.net.SocketException: Socket closed" > ----------------------------------------------------------------------------------------------- > > Key: ISPN-5506 > URL: https://issues.jboss.org/browse/ISPN-5506 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 7.2.1.Final, 8.0.0.Alpha1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.CR1 > > Attachments: infinispan_5506.tgz > > > {code} > testEmbeddedPutRestHotRodGet(org.infinispan.it.compatibility.DistEmbeddedRestHotRodTest) Time elapsed: 0.002 sec <<< FAILURE! > java.net.SocketException: Socket closed > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:589) > at java.net.Socket.connect(Socket.java:538) > at java.net.Socket.<init>(Socket.java:434) > at java.net.Socket.<init>(Socket.java:286) > at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80) > at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122) > at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) > at org.infinispan.it.compatibility.ReplEmbeddedRestHotRodTest.testEmbeddedPutRestHotRodGet(ReplEmbeddedRestHotRodTest.java:80) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5507) Transactions committed immediately before cache stop can block shutdown

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5507?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5507: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Transactions committed immediately before cache stop can block shutdown > ----------------------------------------------------------------------- > > Key: ISPN-5507 > URL: https://issues.jboss.org/browse/ISPN-5507 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 7.2.1.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.2.0.CR1 > > > This is causing random failures in {{DistributedEntryRetrieverTxTest.verifyNodeLeavesBeforeGettingData}}. > The test inserts some values into the cache, starts an iteration, and then kills one of the nodes. In rare instances, the killed cache only receives the TxCompletionCommand for one of the writes after it started the shutdown, and ignores it. That leaves the remote tx on-going, and {{TransactionTable.shutDownGracefully()}} blocks for 30 seconds - causing a {{TimeoutException}} elsewhere in the test. > {noformat} > 10:52:18,129 TRACE (remote-thread-NodeAM-p12133-t6:) [CommandAwareRpcDispatcher] About to send back response SuccessfulResponse{responseValue=null} for command CommitCommand {gtx=GlobalTransaction:<NodeAL-45757>:22325:remote, cacheName='org.infinispan.iteration.DistributedEntryRetrieverTxTest', topologyId=4} > 10:52:18,129 TRACE (testng-DistributedEntryRetrieverTxTest:) [JGroupsTransport] dests=[NodeAM-45518, NodeAL-45757], command=TxCompletionNotificationCommand{ xid=null, internalId=0, topologyId=4, gtx=GlobalTransaction:<NodeAL-45757>:22325:local, cacheName=org.infinispan.iteration.DistributedEntryRetrieverTxTest} , mode=ASYNCHRONOUS, timeout=15000 > 10:52:18,133 DEBUG (testng-DistributedEntryRetrieverTxTest:) [CacheImpl] Stopping cache org.infinispan.iteration.DistributedEntryRetrieverTxTest on NodeAM-45518 > 10:52:18,133 TRACE (OOB-2,NodeAM-45518:) [GlobalInboundInvocationHandler] Attempting to execute CacheRpcCommand: TxCompletionNotificationCommand{ xid=null, internalId=0, topologyId=4, gtx=GlobalTransaction:<NodeAL-45757>:22325:local, cacheName=org.infinispan.iteration.DistributedEntryRetrieverTxTest} [sender=NodeAL-45757] > 10:52:18,133 TRACE (OOB-2,NodeAM-45518:) [GlobalInboundInvocationHandler] Silently ignoring that org.infinispan.iteration.DistributedEntryRetrieverTxTest cache is not defined > 10:52:18,133 DEBUG (testng-DistributedEntryRetrieverTxTest:) [TransactionTable] Wait for on-going transactions to finish for 30 seconds. > 10:52:48,139 WARN (testng-DistributedEntryRetrieverTxTest:) [TransactionTable] ISPN000100: Stopping, but there are 0 local transactions and 1 remote transactions that did not finish in time. > 10:52:48,386 ERROR (testng-DistributedEntryRetrieverTxTest:) [UnitTestTestNGListener] Test verifyNodeLeavesBeforeGettingData(org.infinispan.iteration.DistributedEntryRetrieverTxTest) failed. > java.lang.IllegalStateException: Thread already timed out waiting for event pre_send_response_released > at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:131) > at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:116) > at org.infinispan.iteration.DistributedEntryRetrieverTest.verifyNodeLeavesBeforeGettingData(DistributedEntryRetrieverTest.java:105) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5514) Add test to verify entries are present when utilizing an AsyncStore

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5514?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5514: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Add test to verify entries are present when utilizing an AsyncStore > ------------------------------------------------------------------- > > Key: ISPN-5514 > URL: https://issues.jboss.org/browse/ISPN-5514 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: William Burns > Fix For: 8.2.0.CR1 > > > The AsyncStore can keep entries in memory where they don't exist in the data container or the underlying store. We should verify the various methods of the CacheLoader/AdvancedCacheLoader all work properly when utilizing an AsyncStore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5515) Purge store if there is another node already running

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5515?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5515: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Purge store if there is another node already running > ---------------------------------------------------- > > Key: ISPN-5515 > URL: https://issues.jboss.org/browse/ISPN-5515 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.CR1 > > > Preloading happens before communicating with other nodes that might already have the cache running. When joining the existing members, the cache then waits to receive the first CH in which it is a member, and then deletes only the entries in the segments that it doesn't own in that CH. > The intention of this was to remove as little as possible from the existing data, e.g. if the first node to start up is not the one that was stopped last. But the preloaded entries are not replicated to the other nodes, so this can lead to inconsistencies. > It would be better to delay preloading until we know we are the first node to start up, but failing that we could clear the data container and the store before receiving the initial state. > Note that this will only allow preloading data from one node. Restoring data from more nodes is harder to do, and we will implement it as part of graceful restart. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5510) Provide better Hot Rod client socket timeout and retry defaults

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5510?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5510: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Provide better Hot Rod client socket timeout and retry defaults > --------------------------------------------------------------- > > Key: ISPN-5510 > URL: https://issues.jboss.org/browse/ISPN-5510 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.CR1 > > > The current defaults are: > * Socket timeout = 60 seconds > * Max retries = 10 > As a result of these defaults, if the server hangs an operation, it'd take 10 minutes (60 second timeout x 10 retries) for the operation to finally return an exception to the client, which is way too much. > So, these default value should change to be more aggressive: 30 second socket timeout and 3 max retries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5499) SizeTest.testPersistentDistributedCacheSize random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5499?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5499: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > SizeTest.testPersistentDistributedCacheSize random failures > ----------------------------------------------------------- > > Key: ISPN-5499 > URL: https://issues.jboss.org/browse/ISPN-5499 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.2.0.CR1 > > > {noformat} > 16:04:28,678 ERROR (testng-SizeTest:) [UnitTestTestNGListener] Test testPersistentDistributedCacheSize(org.infinispan.client.hotrod.SizeTest) failed. > java.lang.AssertionError: expected:<20> but was:<38> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252) > at org.infinispan.client.hotrod.SizeTest.testPersistentDistributedCacheSize(SizeTest.java:59) > {noformat} > I have been able to make the test fail reliably by replacing the assertion on line 57 with this: > {code} > for (int i = 0; i < SIZE; i++) { > assertEquals(SIZE, clients.get(0).getCache(cacheName).size()); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5517) JDBCBinaryStore size method should query count directly instead of iterating

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5517?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5517: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > JDBCBinaryStore size method should query count directly instead of iterating > ---------------------------------------------------------------------------- > > Key: ISPN-5517 > URL: https://issues.jboss.org/browse/ISPN-5517 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: William Burns > Assignee: Ryan Emerson > Fix For: 8.0.0.CR1, 8.2.0.CR1 > > > JDBCBinaryStore size method iterates upon all of the rows in the database. We should instead use the getCountRowsSql from the table manipulation just like JDBCStringBasedStore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016