[
https://issues.redhat.com/browse/ISPN-11317?page=com.atlassian.jira.plugi...
]
Diego Lovison updated ISPN-11317:
---------------------------------
Status: Open (was: Pull Request Sent)
See:
https://github.com/infinispan/infinispan/pull/7867#issuecomment-587165950
Dan wrote:
@diegolovison we do not recommend running an Infinispan cluster over a WAN with UDP, so
I'm not sure why this configuration change is needed. It definitely won't make a
difference in our test cluster, where all the machines are just 1 hop away.
Increase Time To Live for UDP protocol
--------------------------------------
Key: ISPN-11317
URL:
https://issues.redhat.com/browse/ISPN-11317
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 11.0.0.Alpha1
Reporter: Diego Lovison
Assignee: Diego Lovison
Priority: Minor
Time to live exceeded
The Time to live (TTL) field in the IPv4 header has a misleading name. Every router that
forwards an IP packet decreases the value of the field by one — it actually has nothing to
do with time at all. In the IPv6 header this field is called “hop limit”. If the TTL value
hits 0, an ICMP message “time to live exceeded” is sent to the dispatcher of the packet.
Meanwhile, some network components drop packets with TTL equal to zero silently. This
mechanism is useful for preventing packets from becoming caught up in an endless routing
loop within your network. The observant reader and network veteran is familiar with this
technique because traceroute uses it to identify all hops that a packet makes on its route
to its destination.
https://www.dynatrace.com/news/blog/detecting-network-errors-impact-on-se...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)