After switching from Azure Cache for Redis (v6.0) to Azure Managed Redis (v7) we get the following errors on cloning of Tasks or deletion of archived tasks:
CROSSSLOT Keys in request don't hash to the same slot (context='', command='del', original-slot='2259', wrong-slot='5440', first-key='tags_d1bd92a3b039400cbafc60a7a5b1e52b_Task', violating-key='tags_d1bd92a3b039400cbafc60a7a5b1e52b_d12eae147f024490a3740fc1453b5076_Task')
With Redis v7 the cluster slots rules enforcing got stricter and Azure Managed Redis always runs with cluster config enabled (even if you just run one node) so you can scale out later as needed.
Despite the error popup the operation still succeeds but not sure if any underlying links might be broken.
This has also been discussed in the ClearML slack: https://clearml.slack.com/archives/CTK20V944/p1760310744908999
After switching from Azure Cache for Redis (v6.0) to Azure Managed Redis (v7) we get the following errors on cloning of Tasks or deletion of archived tasks:
With Redis v7 the cluster slots rules enforcing got stricter and Azure Managed Redis always runs with cluster config enabled (even if you just run one node) so you can scale out later as needed.
Despite the error popup the operation still succeeds but not sure if any underlying links might be broken.
This has also been discussed in the ClearML slack: https://clearml.slack.com/archives/CTK20V944/p1760310744908999