[
https://issues.jboss.org/browse/ISPN-2697?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2697:
------------------------------------
@Radim, I don't know the STABLE code very well, but I think STABILITY messages are
sent in response to STABLE_GOSSIP messages, with a fixed (well, random, but with a fixed
upper limit) delay. So if the STABLE_GOSSIP rate stays constant, the STABILITY rate will
stay constant as well.
I did overlook the STABLE.stability_delay setting, so we should probably require/advise
that sync.replTimeout > 2 * STABLE.desired_avg_gossip + STABLE.stability_delay.
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