@@ -45,7 +45,7 @@ Given the above information, it's recommend to set the minimum configuration val
How to configure this setting:
- In ASP.NET, use the ["minIoThreads" configuration setting](https://msdn.microsoft.com/en-us/library/vstudio/7w2sway1(v=vs.100).aspx) under the `<processModel>` configuration element in web.config. You should be able to set this programmatically (see below) from your Application_Start method in global.asax.cs.
- In ASP.NET, use the ["minIoThreads" configuration setting](https://msdn.microsoft.com/en-us/library/vstudio/7w2sway1(v=vs.100).aspx) under the `<processModel>` configuration element in machine.config. If you are running inside of Azure WebSites, this setting is not exposed through the configuration options. You should be able to set this programmatically (see below) from your Application_Start method in global.asax.cs.
> **Important Note:** the value specified in this configuration element is a *per-core* setting. For example, if you have a 4 core machine and want your minIOThreads setting to be 200 at runtime, you would use `<processModel minIoThreads="50"/>`.
@@ -141,6 +141,7 @@ public virtual bool SetResult(PhysicalConnection connection, Message message, Ra
varserver=bridge.ServerEndPoint;
boollog=!message.IsInternalCall;
boolisMoved=result.AssertStarts(MOVED);
stringerr=string.Empty;
if(isMoved||result.AssertStarts(ASK))
{
message.SetResponseReceived();
...
...
@@ -161,11 +162,19 @@ public virtual bool SetResult(PhysicalConnection connection, Message message, Ra
connection.Multiplexer.Trace(message.Command+" re-issued to "+endpoint,isMoved?"MOVED":"ASK");
returnfalse;
}
else
{
err=string.Format("Endpoint {0} serving hashslot {1} is not reachable at this point of time. Please check connectTimeout value. If it is low, try increasing it to give the ConnectionMultiplexer a chance to recover from the network disconnect.",endpoint,hashSlot);