Allow Auto Slot Migrator to Support Hostnames When ClusterPreferredEndpointType is hostname #1561
Description
Feature request type
sample request
Is your feature request related to a problem? Please describe
As of Garnet 1.0.94, the Automatic Slot Migration uses IP address of the remote host.
The is okay when you are using ClusterPreferredEndpointType is ip. However, when you use ClusterPreferredEndpointType as hostname, then it becomes a bit tedious to per
Describe the solution you'd like
Allow the following syntax to be supported in the migrate command.
MIGRATE remote-hostname-01 6379 "" 0 -1 REPLACE AUTH2 myuser 'mypassword' SLOTSRANGE 8192 16383
The current behaviour is
MIGRATE ip-address-of-remote-hostname-01 6379 "" 0 -1 REPLACE AUTH2 myuser 'mypassword' SLOTSRANGE 8192 16383
It would be good if the MIGRATE command also use the hostname->ip address mapping.
Describe alternatives you've considered
Currently, you have to perform a CLUSTER NODES query to get the hostname and ip address, and the perform the hostname -> ip address mapping yourself. It works fine, but it's not convenient.
Additional context
No response