Strange new message about multiple service endpoints

[johnkwaters]

Just noticed this in the log output, this is new:

Microsoft.Azure.SignalR.ServiceEndpointManager[1]
2 endpoints to https://northstardevsignalr.service.signalr.net found, use the one https://northstardevsignalr.service.signalr.net

Using Azure SignalR - what gives?

[halter73]

@chenkennt ideas? Could this be caused by the new multi-instance (sharding) SDK updates?

[chenkennt]

Yes, we just changed the way how connection strings are read from configuration to support multiple instances. The most probable reason you see this is that you have two Azure_SignalR_ConnectionString in configuration (for example, one in env variable, one in app settings).

With this multiple instance support you'll be able to connect multiple SignalR instances together to handle more connections. Some docs can be found here:
https://github.com/Azure/azure-signalr/blob/dev/docs/sharding.md

/cc @vicancy

[johnkwaters]

I have narrowed it down further. I only have one connection string (if I change it's name, AddAzureSignalR throws the appropriate exception for a missing connection string).
But: I do AddSignalR when configuring DI:

services.AddSignalR().AddAzureSignalR().AddJsonProtocol( options => { options.PayloadSerializerSettings.ReferenceLoopHandling = ReferenceLoopHandling.Ignore; });
And later, UseSignalR when configuring the HTTP pipeline:

app.UseAzureSignalR(routes => { routes.MapHub<StopsHub>("/stops"); });

This is when I get that warning.

Should one no longer do Add and Use like this?

[vicancy]

Hi @johnkwaters Thanks for reporting this, we will fix it. Created Azure/azure-signalr#439 to track it.

[analogrelay]

Closing this as the issue is in the Azure SignalR Service SDK. See the linked issue for more details on the progress!