Why Is the Health Check Status Inherited by PeerID During Reload?

[c1390528]

I have a cluster that contains two servers. The health check of the first server is down and the second server is OK. When I delete the first server and retain the second server, after reload , the second server is immediately set to Down.This is because the peer status is updated based on the peer ID.See:

lua-resty-upstream-healthcheck/lib/resty/upstream/healthcheck.lua

Line 378 in 346f3a6

local key = gen_peer_key("d:", u, is_backup, id)

To solve this problem, can we use the name of the peer to identify a peer instead of the ID?