[infinispan-issues] [JBoss JIRA] (ISPN-1965) Some entries not available during view change
[
https://issues.jboss.org/browse/ISPN-1965?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-1965:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug
808623|https://bugzilla.redhat.com/show_bug.cgi?id=808623]
Technical note updated. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
Diffed Contents:
@@ -1 +1,5 @@
-CCFR - Michal Linhard. If this only pertains to Infiniband/RDMA, then this is a low prio
and non-critical to JDG 6.+CCFR - Michal Linhard. If this only pertains to
Infiniband/RDMA, then this is a low prio and non-critical to JDG 6.
+
+This is a new bug not yet thoroughly investigated.
+
+I can only tell the symptoms: during a view change (probably when a partition occurs)
some entries aren't available to certain clients although they exist somewhere in the
cluster - it was loaded in the data loading phase. The data isn't lost though. Total
number of entries (retrieved via JMX) is correct throughout the test. These errors occurs
only during a brief period of time and then cease.
Some entries not available during view change
---------------------------------------------
Key: ISPN-1965
URL: https://issues.jboss.org/browse/ISPN-1965
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.1.3.FINAL
Reporter: Michal Linhard
Assignee: Dan Berindei
In the 4 node, dist mode, num-owners=2, elasticity test
http://www.qa.jboss.com/~mlinhard/hyperion/run44-elas-dist/
there is a cca 90 sec period of time where clients get null responses to GET
requests on entries that should exist in the cache.
first occurence:
hyperion1139.log 05:31:01,202 286.409
last occurence:
hyperion1135.log 05:32:45,441 390.648
total occurence count: (in all 19 driver nodes)
152241
(this doesn't mean it happens for 152K keys, because each key is retried after
erroneous attempt)
data doesn't seem to be lost, because these errors cease after a while and
number of entries returns back to normal (see cache_entries.csv)
this happens approximately in the period between node0001 is killed and cluster
{node0002 - node0004} is formed (and shortly after).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira