A replicated cache in a zero-capacity node returns incorrect results for some operations. I was able to verify operations that iterate in the cache contents (entries, keys, size) will always return empty, since the node is zero-capacity. Keyed operations, like gets, will correctly redirect the request and return the expected values.

This behavior affects operations like backup/restore with the operator and likely HR rolling upgrades of replicated caches. Anything that relies on iterating in the cache through a zero-capacity node.