[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
Thu Jan 10 10:31:09 EST 2013


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

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

Radim,

the time-based gossip interval is:
{code}
 long computeSleepTime() {
     return getRandom((mbrs.size() * desired_avg_gossip * 2));
 }

 long getRandom(long range) {
     return (long)((Math.random() * range) % range);
 }
{code}


There's also a size based stability, which triggers when a certain number of bytes have been received. The time interval is quite high because we don't want too much traffic from STABLE, and if there's a lot of traffic, the size-based trigger will do the job.


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