Details
-
Bug
-
Resolution: Done
-
Critical
-
5.2.0.Beta6
-
None
Description
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.
Attachments
Issue Links
- is related to
-
JGRP-1570 STABLE: desired_avg_gossip leads to long intervals between reception of STABILITY messages in large clusters
- Resolved