'Renews' 和 'Renews threshold' 在 Eureka 中是什么意思
What does 'Renews' and 'Renews threshold' mean in Eureka
我是 Eureka 的新手，我是从我的 Eureka 服务器 (localhost:8761/) 的主页上看到这些信息的。我没有从官方文档中找到关于 'Renews' 和 'Renews threshold' 的任何解释。任何人都可以解释一下这些词吗？谢谢！
希望对您有所帮助：
更新： 服务器从客户端收到的心跳总数
更新阈值：控制Eureka“自我保护模式”的开关。如果“更新”低于“更新阈值”，则“自我保护模式”开启。
自保模式：
When the Eureka server comes up, it tries to get all of the instance registry information from a neighboring node. If there is a problem getting the information from a node, the server tries all of the peers before it gives up. If the server is able to successfully get all of the instances, it sets the renewal threshold that it should be receiving based on that information. If any time, the renewals falls below the percent configured for that value (below 85% within 15 mins), the server stops expiring instances to protect the current instance registry information.
In Netflix, the above safeguard is called as self-preservation mode and is primarily used as a protection in scenarios where there is a network partition between a group of clients and the Eureka Server. In these scenarios, the server tries to protect the information it already has. There may be scenarios in case of a mass outage that this may cause the clients to get the instances that do not exist anymore. The clients must make sure they are resilient to eureka server returning an instance that is non-existent or un-responsive. The best protection in these scenarios is to timeout quickly and try other servers.
详情请参考Eureka wiki。
我是 Eureka 的新手，我是从我的 Eureka 服务器 (localhost:8761/) 的主页上看到这些信息的。我没有从官方文档中找到关于 'Renews' 和 'Renews threshold' 的任何解释。任何人都可以解释一下这些词吗？谢谢！
希望对您有所帮助：
更新： 服务器从客户端收到的心跳总数
更新阈值：控制Eureka“自我保护模式”的开关。如果“更新”低于“更新阈值”，则“自我保护模式”开启。
自保模式：
When the Eureka server comes up, it tries to get all of the instance registry information from a neighboring node. If there is a problem getting the information from a node, the server tries all of the peers before it gives up. If the server is able to successfully get all of the instances, it sets the renewal threshold that it should be receiving based on that information. If any time, the renewals falls below the percent configured for that value (below 85% within 15 mins), the server stops expiring instances to protect the current instance registry information.
In Netflix, the above safeguard is called as self-preservation mode and is primarily used as a protection in scenarios where there is a network partition between a group of clients and the Eureka Server. In these scenarios, the server tries to protect the information it already has. There may be scenarios in case of a mass outage that this may cause the clients to get the instances that do not exist anymore. The clients must make sure they are resilient to eureka server returning an instance that is non-existent or un-responsive. The best protection in these scenarios is to timeout quickly and try other servers.
详情请参考Eureka wiki。