AWS Elasticache Redis as SignalR Backplane

3
votes

Has anybody tried to connect AWS Elasticache Redis (cluster mode disabled) to use with SignalR? I see there are some serious configuration issues and limitations with AWS Redis.

1) We are trying to use Redis as a backplane for signalr,

//GlobalHost.DependencyResolver.UseRedis("xxxxxx.0001.use1.cache.amazonaws.com:6379", 6379, "", "Performance");

It has to be as simple as this as per docs, I get socket failure on Ping when I try to connect. (I have seen posts about this with Windows azure, but could not find any help articles with AWS)

2) Should the cluster mode have to enabled ? as with cluster mode disabled, we need to use the replica end points for reading, and signalr does not know this ?

Thanks in advance.

2
amazon-web-servicesredissignalramazon-elasticachesignalr-backplane
Please try to ask a specific question for a specific issue. This question is too broad; see stackoverflow.com/help/how-to-ask – Friedrich 'Fred' Clausen
its updated, let me know if its still too broad, thanks ! – jamesb

2 Answers

1
votes

This note (https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-redis) says "SignalR scaleout with Redis does not support Redis clusters.".

Also, perhaps remove ":6379" from the server and only have 6379 in the port?

1
votes

We finally resolved, by removing the clusters and making a standalone AWS Redis.

The other issue we had it was assigned to the wrong security group, so we had changed it to the same as our EC2 instances.

You will still need to include ":6379" while accessing the DB.

However, if you are using dependency resolver for signalr you should not include ":6379" as the access point, but if you use the redis for read and write operations using StackExchange.Redis then you need to include ":6379" in the request.