多线程并发下,出现连接问题

[ZhouSCH]

环境

FreeRedis 1.2.2
redis 7.2.3
ubuntu 20.04

测试代码

using System.Text.Json;
using FreeRedis;

namespace freeRedisTest
{
    internal class FreeRedis1
    {
        public static Lazy<RedisClient> Client = new Lazy<RedisClient>(() =>
        {
            return new RedisClient("127.0.0.1:6379");
        });

        private static RedisClient cli => Client.Value;

        public static void Run()
        {
            Console.WriteLine("begin");
            int loopCount = 100000;
            while (loopCount-- > 0)
            {
                int count = loopCount;
                var task = Task.Run(() =>
                {
                    Console.WriteLine($"{count}run task");
                    Test test = new()
                    {
                        test1 = $"{count}",
                        test2 = 222,
                        test3 = 443,
                    };

                    try
                    {
                        var value = JsonSerializer.Serialize(test);
                        cli.Set($"test_{count}", value);

                        value = cli.Get($"test_{count}");
                        var d = JsonSerializer.Deserialize<Test>(value);
                        Console.WriteLine($"{count} complete {d.test1}");
                    }
                    catch (Exception ex)
                    {
                        Console.WriteLine(ex);
                    }
                });
            }

            Console.ReadLine();
        }
    }
}

运行这个测试。windows完全没有问题，放在Ubuntu就会有问题而且每次必出。我重新实例了一个aws云服务器。放上去跑也会出现同样的问题。
错误如下:

 ---> System.TimeoutException: Connect to redis-server(127.0.0.1:6379) timeout, DEBUG: Dns.GetHostEntry(127.0.0.1)=System.Net.IPHostEntry
   at FreeRedis.Internal.DefaultRedisSocket.Connect() in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\Internal\DefaultRedisSocket.cs:line 255
   at FreeRedis.Internal.DefaultRedisSocket.Write(CommandPacket cmd) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\Internal\DefaultRedisSocket.cs:line 164
   at FreeRedis.RedisClient.SingleInsideAdapter.<>c__DisplayClass5_0`1.<AdapterCall>b__0() in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient\Adapter\SingleInsideAdapter.cs:line 47
   at FreeRedis.RedisClient.LogCallCtrl[T](CommandPacket cmd, Func`1 func, Boolean aopBefore, Boolean aopAfter) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient.cs:line 98
   at FreeRedis.RedisClient.LogCall[T](CommandPacket cmd, Func`1 func) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient.cs:line 93
   at FreeRedis.RedisClient.SingleInsideAdapter.AdapterCall[TValue](CommandPacket cmd, Func`2 parse) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient\Adapter\SingleInsideAdapter.cs:line 45
   at FreeRedis.RedisClient.Call[TValue](CommandPacket cmd, Func`2 parse) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient.cs:line 91
   at FreeRedis.RedisClient.Ping(String message) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient\Connection.cs:line 94
   at FreeRedis.Internal.RedisClientPoolPolicy.PrevReheatConnectionPool(ObjectPool`1 pool, Int32 minPoolSize) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\Internal\RedisClientPool.cs:line 248
   --- End of inner exception stack trace ---
   at FreeRedis.Internal.ObjectPool.ObjectPool`1.GetFree(Boolean checkAvailable) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\Internal\ObjectPool\ObjectPool.cs:line 292
   at FreeRedis.Internal.ObjectPool.ObjectPool`1.Get(Nullable`1 timeout) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\Internal\ObjectPool\ObjectPool.cs:line 323
   at FreeRedis.RedisClient.PoolingAdapter.GetRedisSocket(CommandPacket cmd) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient\Adapter\PoolingAdapter.cs:line 61
   at FreeRedis.RedisClient.PoolingAdapter.<>c__DisplayClass9_0`1.<AdapterCall>b__0() in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient\Adapter\PoolingAdapter.cs:line 74
   at FreeRedis.RedisClient.LogCallCtrl[T](CommandPacket cmd, Func`1 func, Boolean aopBefore, Boolean aopAfter) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient.cs:line 98
   at FreeRedis.RedisClient.LogCall[T](CommandPacket cmd, Func`1 func) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient.cs:line 93
   at FreeRedis.RedisClient.PoolingAdapter.AdapterCall[TValue](CommandPacket cmd, Func`2 parse) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient\Adapter\PoolingAdapter.cs:line 70
   at FreeRedis.RedisClient.Call[TValue](CommandPacket cmd, Func`2 parse) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient.cs:line 91
   at FreeRedis.RedisClient.Set[T](String key, T value, TimeSpan timeout, Boolean keepTtl, Boolean nx, Boolean xx, Boolean get) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient\Strings.cs:line 1279
   at FreeRedis.RedisClient.Set[T](String key, T value, Int32 timeoutSeconds) in D:\test_project\freeRedisTest\FreeRedis\src\FreeRedis\RedisClient\Strings.cs:line 1118
   at freeRedisTest.FreeRedis1.<>c__DisplayClass3_0.<Run>b__0() in D:\test_project\freeRedisTest\FreeRedis.cs:line 42

我用工具Profiler了redis的状态，发现一个信息都没有收到。连接前的Ping CheckAvailable 也没有收到。

[2881099]

测试一下，十万个HTTP请求会不会超时

[ZhouSCH]

#163 (reply in thread)
我可以把这个合库里，提一个pr吗？我看了几个C#的库都有这个问题，我感觉StackExchange.Redis timeout也是这个原因导致的.我现在的系统使用到大量的Task.Run的异步操作，压测非常容易出现这个timeout问题

[2881099]

用 Task.WaitAll 不如用 StartPipeline

[2881099]

写法挺奇怪，并且 .Connect 必报错，这对开发者在 vs 环境弹出错误框太不友好。
如果有需要可以在本地修改源码运行，暂时不接受这次PR，如果有好的改进方案，欢迎讨论反馈，谢谢。

[ZhouSCH]

抛出是因为设置了blocking，非阻塞模式正常抛出，因为socket.Poll底层是select模型的简单用法，所以写法是这样。c和c++应该会有这种类似的源码。只不过他抛出的错误是自己去获取。如果实在不能接受，没关系的。感谢你的开源项目

[ZhouSCH]

我印象中记得好像sendtimeout会影响connect连接超时，如果可以的直接设置这个属性就可以做同步超时。这样就可以不用不阻塞模式。也可以不用select做超时。我明天实验下。这样也可以绕过线程资源的竞争

[ZhouSCH]

我印象中记得好像sendtimeout会影响connect连接超时，如果可以的直接设置这个属性就可以做同步超时。这样就可以不用不阻塞模式。也可以不用select做超时。我明天实验下。这样也可以绕过线程资源的竞争

无语，只有linux的socket设置才有效，那就这样吧