Hot slot when using { and } in the cache key.

[dearcherian]

Version 5.0.3.RELEASE

clusterKeyslot method uses the string inside { and } in cachekey and omits everything outside for generating the slot. We found that when we set the cache this particular node is getting 10X more traffic and we found that our cache key was using { and } causing it direct it to the same node creating a hot node. The screenshot shows all the cacheKeys generate the same slot number 12307

The set command in RedisAdvancedClusterAsyncCommands should be using the same logic to derive the slot number.

Since it is not explicitly expected or since the methods are not throwing any error in using { and } I consider this as a bug.

Caching is working fine only the slot number derivation logic is not working properly.