[infinispan-issues] [JBoss JIRA] (ISPN-2697) HotRodServer startup fails when its record cannot be inserted into topology cache
[
https://issues.jboss.org/browse/ISPN-2697?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2697:
----------------------------------------
Talking to Bela yesterday, adding the flag is the quickest solution here and I've
narrowed down the use case when to use the flag, so it will be accompanied by plenty of
javadoc and I'll blog about it. That said, a solution that doesn't require the
flag would be ideal, as Dan suggested, that allows STABLE to cover this situations given
the replication timeout value.
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