help request: 负载策略采用chash时，如果没有key，默认是根据remote_addr hash，可是客户端ip比较固定，能不能如果没key，就round-robin轮询。

[hnzhuzi]

Description

负载策略采用chash时，如果没有key，默认是根据remote_addr hash，可是客户端ip比较固定，能不能如果没key，就round-robin轮询。

Environment

• APISIX version (run apisix version): 3.8

[hnzhuzi]

When the load strategy uses chash, if there is no key, the default is based on remote_addr hash, but the client IP is relatively fixed(all traffic will visit a single node). If there is no key, can round-robin polling be performed?

[wklken]

It's reasonable to use a default key to chash then choose the upstream (It would be much more complex if use a fallback strategy)

I think you should check what key can be performed like RR, or just use RR directly.

[hnzhuzi]

It's reasonable to use a default key to chash then choose the upstream (It would be much more complex if use a fallback strategy)

I think you should check what key can be performed like RR, or just use RR directly.

Currently, this requirement is achieved by modifying the code. If the request does not have a key, the time hash is used by default:
if not chash_key then
chash_key = tostring(ngx.time())
end
I would like to know if there is a way without changing the code, such as through a plug-in.

[wklken]

you can test the vars of nginx here https://nginx.org/en/docs/varindex.html.

time_local as the key?

[hnzhuzi]

you can test the vars of nginx here https://nginx.org/en/docs/varindex.html.

time_local as the key?

Can this be done without modifying the code, but still meet my needs? If the request header has a key, use the key hash. If there is no key, the default is based on the time key (the effect is similar to round-robin).

[wklken]

I don't think so.

you can clone the project, modify the code and generate a patch file, and patch it after installed (or during build image).