[
https://issues.jboss.org/browse/ISPN-3613?page=com.atlassian.jira.plugin....
]
William Burns edited comment on ISPN-3613 at 10/9/13 9:56 PM:
--------------------------------------------------------------
I am unable to reproduce this with the latest code base. Digging further it appears this
was fixed by ISPN-2903.
Side note: the xml file provided is not accurate as the log shows L1 was enabled for the
cache, but the xml didn't have it enabled.
But it looks like this is caused because eviction was enabled and a rehash causes old
values to be evicted. When it was evicted it would notify the cache loader that it was
removed with ISPN-2903 and would then remove it from the store as well.
I will add a test that confirms this.
Also I need to verify if when sharing is disabled if it properly removes the entries from
the cache store.
was (Author: william.burns):
I am unable to reproduce this with the latest code base. Digging further it appears
this was fixed by ISPN-2903.
Side note: the xml file provided is not accurate as the log shows L1 was enabled for the
cache, but the xml didn't have it enabled.
But it looks like this is caused because eviction was enabled and a rehash causes old
values to be evicted. When it was evicted it would notify the cache loader that it was
removed with ISPN-2903 and would then remove it from the store as well.
I will add a test that confirms this.
Also I need to verify if when sharing is disabled if it properly evicts the entries from
the cache store.
Stored entries are deleted from table in rebalance
--------------------------------------------------
Key: ISPN-3613
URL:
https://issues.jboss.org/browse/ISPN-3613
Project: Infinispan
Issue Type: Bug
Reporter: Mircea Markus
Assignee: William Burns
Labels: jdg62GAblocker
Fix For: 6.0.0.CR2, 6.0.0.Final
Description of problem:
When passivation value is false, stored entries are deleted from table in rebalance.
clustered.xml
------------
<distributed-cache name="myCache" mode="SYNC"
start="EAGER">
<locking isolation="READ_COMMITTED" acquire-timeout="30000"
concurrency-level="1000" striping="false"/>
<transaction mode="NONE"/>
<eviction strategy="LIRS" max-entries="10000"/>
<string-keyed-jdbc-store datasource="java:jboss/datasources/InfinispanDS"
passivation="false" preload="true" purge="false"
shared="true" fetch-state="false">
...
Version-Release number of selected component (if applicable):
JDG 6.1
How reproducible:
I will attache the clustered.xml and trace logs.
Steps to Reproduce:
1.start node1
2.put 300 entries
3.start node2
check entries:
select count(*) from table;
300
4.start node3
check entries:
select count(*) from table;
0
Actual results:
In step 4, number of entries are 0 in DB table.
Expected results:
In step 4, number of entries are 300 in DB table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira