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

[Dan Berindei (JIRA)]

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

Dan Berindei commented on ISPN-2697:
------------------------------------

[~belaban], as I said earlier, state transfer commands use another hack to set the RSVP flag on the message. We do need that hack, regardless of any GUARANTEED_DELIVERY flag in the cache API, because none of the state transfer commands have flags.

I agree with Galder: sync mode implies guaranteed delivery. The configuration should either combine a low replTimeout with a low desired_avg_gossip, or a high replTimeout with a high desired_avg_gossip. I don't see why we should go out of our way to support a configuration with a low replTimeout and a high desired_avg_gossip.
                
> 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
>            Priority: Critical
>             Fix For: 5.2.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