[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1016) Hash-aware view update causing lock ups in Hot Rod

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-1016:
----------------------------------------

Something to bear in mind is whether rehashing would be something that could block startup? Well, the node starting up would have finished rehashing as far as it is concerned cos all caches are started before that. However, other nodes might be starting up and this node could be adjacent to them and so a union CH could be in action. So, the easiest would be to wait for rehash to finish (a similar timeout as rehash join task? rehash rpc timeout * 10)

> Hash-aware view update causing lock ups in Hot Rod
> --------------------------------------------------
>
>                 Key: ISPN-1016
>                 URL: https://issues.jboss.org/browse/ISPN-1016
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>    Affects Versions: 4.2.1.FINAL
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 4.2.2.BETA1, 5.0.0.BETA1
>
>
> When encoding a Hot Rod response, if the encoder discovers that the client has an old view, it decides that a new topology needs to be sent to the client. Now, when building this view in distributed caches, the encoder checks whether in the new view, any of the nodes hash ids has changed, and if so, it sends a cluster wide replace with the view containing the new hash ids.
> This seems to cause some deadlocks as shown in JBPAPP-6113 where one node is timing to send the replace to other node, and another node is timing out doing the same. This needs further thinking but have some ideas in mind...
> On top of that, it appears that a failure here is causing problems the requests after that, so some thinking needs to be done to see if that replace() call can be moved out of there...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira