GlobalConfiguration.Configuration.UseRedisStorage(@"192.168.0.3:7002",

new Hangfire.Redis.RedisStorageOptions

{

Prefix = "{hangfire-A}:",

// Db =2

});

app.UseHangfireDashboard();

Key has MOVED from Endpoint 127.0.0.1:7001 and hashslot 6991 but CommandFlags.NoRedirect was specified - redirect not followed for MGET. IOCP: (Busy=0,Free=1000,Min=4,Max=1000), WORKER: (Busy=1,Free=32766,Min=4,Max=32767), Local-CPU: n/a

Redis Cluster support¶

You can use a single endpoint to connect to a Redis cluster, Hangfire will detect other instances automatically by querying the node configuration. However, it’s better to pass multiple endpoints in order to mitigate connectivity issues, when some of endpoints aren’t available, e.g. during the failover process.

Since Hangfire requires transactions, and Redis doesn’t support ones that span multiple hash slots, you also need to configure the prefix to assign it to the same hash tag:

GlobalConfiguration.Configuration.UseRedisStorage(
    "localhost:6379,localhost:6380,localhost:6381",
    new RedisStorageOptions { Prefix = "{hangfire-1}:" });

This will bind all the keys to a single Redis instance. To be able to fully utilize your Redis cluster, consider using multiple JobStorage instances and leveraging some load-balancing technique (round-robin is enough for the most cases). To do so, pick different hash tags for different storages and ensure they are using hash slots that live on different masters by using commands CLUSTER NODES and CLUSTER KEYSLOT.

来自 <http://docs.hangfire.io/en/latest/configuration/using-redis.html>

GlobalConfiguration.Configuration.UseRedisStorage(@"192.168.0.3:7002",

new Hangfire.Redis.RedisStorageOptions

{

Prefix = "{hangfire-A}:",

// Db =2

});