[
https://issues.jboss.org/browse/ISPN-2697?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2697:
------------------------------------
All the flags we have so far are related to cache operations, and are not relevant for
state transfer commands. That's the reason state transfer commands to not carry any
flags.
I'm not saying that we absolutely shouldn't use a flag for the HotRod server
startup issue, I'm just saying it won't be in any way related to the way the RSVP
flag is added for the state transfer commands.
OTOH I *am* saying that I don't see the reason for adding a new flag, when this can be
handled much easier by adjusting the replTimeout and desired_avg_gossip settings.
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