[infinispan-issues] [JBoss JIRA] (ISPN-2262) Unresponsiveness in resilience test
Radim Vansa (JIRA)
jira-events at lists.jboss.org
Mon Sep 10 07:08:32 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716937#comment-12716937 ]
Radim Vansa commented on ISPN-2262:
-----------------------------------
Well, I've generated another situation without so many exceptions but where the newly started cache waits for state transfer (and it does not happen). I have uploaded the logs (again pretty big) on http://dl.dropbox.com/u/103079234/serverlogs_waiting.zip
> 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: Dan Berindei
> Priority: Critical
> Fix For: 5.2.0.Final
>
>
> 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
More information about the infinispan-issues
mailing list