[infinispan-issues] [JBoss JIRA] (ISPN-2262) Unresponsiveness in resilience test
[
https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-2262:
-----------------------------------
In fact, I am not sure what to do with this. I have similar issues both on
5.1.7.-redhat-1. When I prolonged the test duration for older "marked as
working" resilience tests I sometimes get really a lot of exceptions, e.g. I have
noticed that some node did not unlocked some key (and other nodes fail requesting it), or
just the timeouts... I don't think I can solve the problem without any help. Could
someone take a brief look on the enclosed logs, or should I produce some logs from 5.1.7?
Usually these are huge (gigabytes on trace level for org.infinispan.*).
Unresponsiveness in resilience test
-----------------------------------
Key: ISPN-2262
URL: https://issues.jboss.org/browse/ISPN-2262
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 5.2.0.Alpha3
Reporter: Radim Vansa
Assignee: Mircea Markus
Priority: Critical
Basic resilience scenario in library mode:
* spawn 4 nodes
* kill one node (kill = insert DISCARD protocol and then call CacheManger.stop())
* start one node
We use RadarGun (with some modifications) for this test.
When the node is started again the system looses some messages as some timeouts are
triggered (and the RadarGun stage acknowledgement is missing as well) and later put/get
requests cause exceptions.
The trace logs are too big, therefore, these are published on
http://dl.dropbox.com/u/103079234/serverlogs_trace.zip
Note that the test was shutdown manually.
--
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