[infinispan-issues] [JBoss JIRA] (ISPN-2697) HotRodServer startup fails when its record cannot be inserted into topology cache

[Radim Vansa (JIRA)]

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

Radim Vansa commented on ISPN-2697:
-----------------------------------

OK, I have revised the code and you are right (of course ;-)). Maybe the doc (I mean both in-code doc and design doc which does not mention retransmission at all) should be more verbose about retransmission and not only garbage collection.
Do I understand it correctly now, that the stability message which triggers retransmission is only sent after all gossips are collected. If the whole cluster sends in average one of these gossips every X seconds (where default X is 20, we use 5), the stability message will be sent only every (clusterSize * X) seconds? (in our 64 node cluster this is 5 minutes 20 seconds)? That seems like a long time to me.

                
> HotRodServer startup fails when its record cannot be inserted into topology cache
> ---------------------------------------------------------------------------------
>
>                 Key: ISPN-2697
>                 URL: https://issues.jboss.org/browse/ISPN-2697
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Remote protocols
>    Affects Versions: 5.2.0.Beta6
>            Reporter: Radim Vansa
>            Assignee: Galder Zamarreño
>             Fix For: 5.3.0.Final
>
>
> When the HotRodServer starts it inserts its record to __hotRodTopologyCache ({{HotRodServer.addSelfToTopologyView(...)}}).
> However, this put may very easily fail - as the command is broadcasted using NAKACK2 protocol, if the message gets lost and there's no following broadcasted message, the message will be not retransmitted and the put operation times out (Replication timeout), which fails the whole HotRodServer startup, all because of one lost UDP message.

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