[JBoss JIRA] (ISPN-4889) SimpleLuceneTest.testCacheReuse random failures
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4889?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-4889 at 12/4/14 11:27 AM:
-------------------------------------------------------------------
Was able to reproduce with:
{code}
loop 100 taskset -c 0,1 mvn test | tee log.txt
{code}
where loop is defined as
{code}
function loop { seq 1 $1| { shift; xargs -i -- "$@"; } }
{code}
The issue seems to be the same as to other similar randomly failing tests in the lucene directory suite. For some reason, sometimes, there's a key in the Chunkcache with no value, so doing:
{code}
Object value = cache.get(existingChunkKey);
{code}
returns null, being the key obtained from {{cache.keySet()}}
was (Author: gustavonalle):
Was able to reproduce with:
{code}
loop 100 taskset -c 0,1 mvn test | tee log.txt
{code}
where loop is defined as
{code}
function loop { seq 1 $1| { shift; xargs -i -- "$@"; } }
{code}
The issue seems to be the same as to other similar randomly failing tests in the lucene directory suite. For some reason, sometimes, there's a key in the Chunkcache with no value, so doing:
{code}
Object value = cache.get(existingChunkKey);
{code}
returns null.
> SimpleLuceneTest.testCacheReuse random failures
> -----------------------------------------------
>
> Key: ISPN-4889
> URL: https://issues.jboss.org/browse/ISPN-4889
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Query
> Affects Versions: 7.0.0.CR2
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> http://ci.infinispan.org/project.html?projectId=Infinispan&buildTypeId=&t...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4889) SimpleLuceneTest.testCacheReuse random failures
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4889?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-4889 at 12/4/14 11:25 AM:
-------------------------------------------------------------------
Was able to reproduce with:
{code}
loop 100 taskset -c 0,1 mvn test | tee log.txt
{code}
where loop is defined as
{code}
function loop { seq 1 $1| { shift; xargs -i -- "$@"; } }
{code}
The issue seems to be the same as to other similar randomly failing tests in the lucene directory suite. For some reason, soemtimes, there's a key in the Chunkcache with no value, so doing:
{code}
Object value = cache.get(existingChunkKey);
{code}
returns null.
was (Author: gustavonalle):
Was able to reproduce with:
{code}
loop 100 taskset -c 0,1 mvn test | tee log.txt
{code}
where loop is defined as
{code}
function loop { seq 1 $1| { shift; xargs -i -- "$@"; } }
{code}
The issue seems similar to other similar randomly failing tests. For some reason, soemtimes, there's a key in the Chunkcache with no value, so doing:
{code}
Object value = cache.get(existingChunkKey);
{code}
returns null.
> SimpleLuceneTest.testCacheReuse random failures
> -----------------------------------------------
>
> Key: ISPN-4889
> URL: https://issues.jboss.org/browse/ISPN-4889
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Query
> Affects Versions: 7.0.0.CR2
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> http://ci.infinispan.org/project.html?projectId=Infinispan&buildTypeId=&t...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4889) SimpleLuceneTest.testCacheReuse random failures
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4889?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-4889 at 12/4/14 11:25 AM:
-------------------------------------------------------------------
Was able to reproduce with:
{code}
loop 100 taskset -c 0,1 mvn test | tee log.txt
{code}
where loop is defined as
{code}
function loop { seq 1 $1| { shift; xargs -i -- "$@"; } }
{code}
The issue seems to be the same as to other similar randomly failing tests in the lucene directory suite. For some reason, sometimes, there's a key in the Chunkcache with no value, so doing:
{code}
Object value = cache.get(existingChunkKey);
{code}
returns null.
was (Author: gustavonalle):
Was able to reproduce with:
{code}
loop 100 taskset -c 0,1 mvn test | tee log.txt
{code}
where loop is defined as
{code}
function loop { seq 1 $1| { shift; xargs -i -- "$@"; } }
{code}
The issue seems to be the same as to other similar randomly failing tests in the lucene directory suite. For some reason, soemtimes, there's a key in the Chunkcache with no value, so doing:
{code}
Object value = cache.get(existingChunkKey);
{code}
returns null.
> SimpleLuceneTest.testCacheReuse random failures
> -----------------------------------------------
>
> Key: ISPN-4889
> URL: https://issues.jboss.org/browse/ISPN-4889
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Query
> Affects Versions: 7.0.0.CR2
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> http://ci.infinispan.org/project.html?projectId=Infinispan&buildTypeId=&t...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4889) SimpleLuceneTest.testCacheReuse random failures
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4889?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-4889 at 12/4/14 11:25 AM:
-------------------------------------------------------------------
Was able to reproduce with:
{code}
loop 100 taskset -c 0,1 mvn test | tee log.txt
{code}
where loop is defined as
{code}
function loop { seq 1 $1| { shift; xargs -i -- "$@"; } }
{code}
The issue seems similar to other similar randomly failing tests. For some reason, soemtimes, there's a key in the Chunkcache with no value, so doing:
{code}
Object value = cache.get(existingChunkKey);
{code}
returns null.
was (Author: gustavonalle):
Was able to reproduce with:
{code}
loop 100 taskset -c 0,1 mvn test | tee log.txt
{code}
where loop is defined as
{code}
function loop { seq 1 $1| { shift; xargs -i -- "$@"; } }
{code}
The issue seems similar to other similar tests. For some reason, soemtimes, there's a key in the Chunkcache with no value, so doing:
{code}
Object value = cache.get(existingChunkKey);
{code}
returns null.
> SimpleLuceneTest.testCacheReuse random failures
> -----------------------------------------------
>
> Key: ISPN-4889
> URL: https://issues.jboss.org/browse/ISPN-4889
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Query
> Affects Versions: 7.0.0.CR2
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> http://ci.infinispan.org/project.html?projectId=Infinispan&buildTypeId=&t...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5047) Partition handling user guide is outdated
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5047:
----------------------------------
Summary: Partition handling user guide is outdated
Key: ISPN-5047
URL: https://issues.jboss.org/browse/ISPN-5047
Project: Infinispan
Issue Type: Bug
Components: Documentation-Core
Affects Versions: 7.1.0.Alpha1, 7.0.2.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 7.1.0.Beta1
* The user guide is missing the JMX availability attribute
* The configuration section says replicated mode is not supported.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5046) PartitionHandling: split during commit can leave the cache inconsistent after merge
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5046:
----------------------------------
Summary: PartitionHandling: split during commit can leave the cache inconsistent after merge
Key: ISPN-5046
URL: https://issues.jboss.org/browse/ISPN-5046
Project: Infinispan
Issue Type: Bug
Components: Core, State Transfer
Affects Versions: 7.1.0.Alpha1, 7.0.2.Final
Reporter: Dan Berindei
Priority: Critical
Fix For: 7.1.0.Beta1
Say we have a cluster ABCD; a transaction T was started on A, with B as the primary owner and C the backup owner. B and C both acknowledge the prepare, and the network splits into AB and CD right before A sends the commit command. Eventually A suspects C and D, but the commit still succeeds on B before C and D are suspected. And SuspectExceptions are ignored for commit commands, so the user won't see any error.
However, C will eventually suspect A and B. When the CD cache topology is installed, it will roll back transaction T. After the merge, both partitions are in degraded mode, so we assume that they both have the latest data and the key is never updated on C.
>From C's point of view, this is very similar to ISPN-3421. The fix should also be similar, we could delay the transaction rollback on C until we get a confirmation from B that T was not committed there. Since B is inaccessible, it will eventually get a SuspectException and the CD cache topology, at which point the cache is in degraded mode and it can wait for a merge. On merge, it should check the status of the transaction on B again, and either commit or rollback based on what B did.
We also need to suspend the cleanup of completed transactions while the cache is in degraded mode, otherwise C might not find T on B after the merge.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months