[infinispan-issues] [JBoss JIRA] (ISPN-2802) Cache recovery fails due to missing responses

[Radim Vansa (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753462#comment-12753462 ] 

Radim Vansa edited comment on ISPN-2802 at 2/11/13 11:21 AM:
-------------------------------------------------------------

I would suspect OOB TP as it's pretty popular nowadays, but it's rather strange what all the threads do when there's no background load in the cluster. I should setup the threadpool monitor here... will do and publish the result.

Btw., I've also tried to run tcpdump on 806 to confirm if the message is received and the issue did not happen. Viva la resistencialism! :-) (http://en.wikipedia.org/wiki/Resistentialism)
                
      was (Author: rvansa):
    I would suspect OOB TP as it's pretty popular nowadays, but it's pretty strange what all the threads do when there's no background load in the cluster. I should setup the threadpool monitor here... will do and publish the result.

Btw., I've also tried to run tcpdump on 806 to confirm if the message is received and the issue did not happen. Viva la resistencialism! :-) (http://en.wikipedia.org/wiki/Resistentialism)
                  
> Cache recovery fails due to missing responses
> ---------------------------------------------
>
>                 Key: ISPN-2802
>                 URL: https://issues.jboss.org/browse/ISPN-2802
>             Project: Infinispan
>          Issue Type: Bug
>          Components: State transfer
>    Affects Versions: 5.2.0.CR3
>            Reporter: Radim Vansa
>            Assignee: Mircea Markus
>
> When the cache recovery is started, the new coordinator sends CacheTopologyControlCommand.GET_STATUS to all nodes and waits for responses. However, I have a reproducible test-case where it always times out waiting for the responses.
> Here are the logs (TRACE is not doable here, but I added some byteman traces - see topology.btm in the archive): http://dl.dropbox.com/u/103079234/recovery.zip
> The problematic spot is on node3 at 05:37:57 receiving cluster view 34.
> All nodes (except the one which is killed, in this case node1) respond quickly to the GET_STATUS command (see BYTEMAN Receiving - Received pairs, these are bound to command execution in CommandAwareRpcDispatcher), but some responses are not received on node3 (look for Receiving rsp bound to GroupRequest).
> JGroups tracing could be useful here but it is not available (intensive logging often blocks on internal log4j locks and the node becomes unresponsive).
> As mentioned above, the case is reproducible, therefore if you can suggest any particular BYTEMAN hook, I can try it.

--
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