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

Bela Ban (JIRA) jira-events at lists.jboss.org
Mon Jan 28 11:27:47 EST 2013


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

Bela Ban commented on ISPN-2697:
--------------------------------

Galder, just use the damn flag ! :-) Others (dberindei) are using it too, so what's wrong with this ?

The alternative is to either have a NAKACK protocol which uses positive acks (like SMACK used to do it), but that won't scale for large clusters, or to use a desired_avg_gossip in STABLE that runs more frequently, but that generates more traffic in large clusters.

I'll look into the latter solution in JGRP-1570, and possibly come up with a STABLE2 as described in that JIRA.

Until this is available, use the flag.
                
> 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



More information about the infinispan-issues mailing list