一次误用CSRedisCore引发的redis故障排除经历
前导
上次Redis MQ分布式改造完成之后， 编排的容器稳定运行了一个多月，昨天突然收到ETL端同事通知，没有采集到解析日志了。
赶紧进服务器看了一下，用于数据接收的receiver容器挂掉了， 尝试docker container start [containerid], 几分钟后该容器再次崩溃。
Redis连接超限
docker log [containerid] 查看容器日志； 重点：CSRedis.RedisException: ERR max number of clients reached
Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker[]
Executed action EqidManager.Controllers.EqidController.BatchPutEqidAndProfileIds (EqidReceiver) in .1767ms
fail: Microsoft.AspNetCore.Server.Kestrel[]
Connection id "0HLPR3AP8ODKH", Request id "0HLPR3AP8ODKH:00000001": An unhandled exception was thrown by the application.
CSRedis.RedisException: ERR max number of clients reached
at CSRedis.CSRedisClient.GetAndExecute[T](RedisClientPool pool, Func` handler, Int32 jump, Int32 errtimes)
at CSRedis.CSRedisClient.ExecuteScalar[T](String key, Func` hander)
at CSRedis.CSRedisClient.LPush[T](String key, T[] value)
at RedisHelper.LPush[T](String key, T[] value)
at EqidManager.Controllers.EqidController.BatchPutEqidAndProfileIds(List` eqidPairs) in /home/gitlab-runner/builds/haD2h5xC//webdissector/datasource/eqid-manager/src/EqidReceiver/Controllers/EqidController.cs:line
at lambda_method(Closure , Object )
at Microsoft.Extensions.Internal.ObjectMethodExecutorAwaitable.Awaiter.GetResult()
at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.AwaitableResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at System.Threading.Tasks.ValueTask`.get_Result()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync()
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication` application)
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[]
Request finished in .9549ms
【dockerhost:/】仍然不可用，下一次恢复检查时间：// ::，错误：(ERR max number of clients reached)
【dockerhost:/】仍然不可用，下一次恢复检查时间：// ::，错误：(ERR max number of clients reached)
【dockerhost:/】仍然不可用，下一次恢复检查时间：// ::，错误：(ERR max number of clients reached)
【dockerhost:/】仍然不可用，下一次恢复检查时间：// ::，错误：(ERR max number of clients reached)【dockerhost:/】仍然不可用，下一次恢复检查时间：// ::，错误：(ERR max number of clients reached) 【dockerhost:/】仍然不可用，下一次恢复检查时间：// ::，错误：(ERR max number of clients reached)
【dockerhost:/】仍然不可用，下一次恢复检查时间：// ::，错误：(ERR max number of clients reached)
docker logs [containerid]
日志上显示连接Redis服务器的客户端数量超限，头脑快速思考，目前编排的某容器使用CSRedisCore 对于16个Redis DB实例化了16个客户端，但Redis服务器也不至于这么不经折腾吧。
赶紧进redis.io官网搜集相关资料。
After the client is initialized, Redis checks if we are already at the limit of the number of clients that it is possible to handle simultaneously (this is configured using the
maxclientsconfiguration directive, see the next section of this document for further information).In case it can't accept the current client because the maximum number of clients was already accepted, Redis tries to send an error to the client in order to make it aware of this condition, and closes the connection immediately. The error message will be able to reach the client even if the connection is closed immediately by Redis because the new socket output buffer is usually big enough to contain the error, so the kernel will handle the transmission of the error.
大致意思是：Redis服务器maxclients配置了最大客户端连接数， 如果当前连接的客户端超限，Redis会回发一个错误消息给客户端，并迅速关闭客户端连接。
立刻登录Redis服务器查看默认配置，确认当前Redis服务器maxclients=10000（这是一个动态值，由maxclients和最大进程文件句柄决定），
# Set the max number of connected clients at the same time. By default
# this limit is set to 10000 clients, however if the Redis server is not
# able to configure the process file limit to allow for the specified limit
# the max number of allowed clients is set to the current file limit
# minus 32 (as Redis reserves a few file descriptors for internal uses).
#
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
# maxclients 10000
左图表明：通过Redis-Cli 登录进服务器立即就被踢下线。
基本可认定redis客户端使用方式有问题。
CSRedisCore使用方式
继续查看相关资料，可在redis服务器上利用redis-cli命令：info clients、client list仔细分析客户端连接。
info clients 命令显示现场确实有10000的连接数；
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=lpush
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
client list命令显示连接如下：
官方对client list命令输出字段的解释：
addr: The client address, that is, the client IP and the remote port number it used to connect with the Redis server.
fd: The client socket file descriptor number.
name: The client name as set by CLIENT SETNAME.
age: The number of seconds the connection existed for.
idle: The number of seconds the connection is idle.
flags: The kind of client (N means normal client, check the full list of flags).
omem: The amount of memory used by the client for the output buffer.
cmd: The last executed command.
根据以上解释，表明 Redis服务器收到很多ip=172.16.1.3（故障容器在网桥内的Ip 地址）的客户端连接，这些连接最后发出的是ping命令（这是一个测试命令）
故障容器使用的Redis客户端是CSRedisCore，该客户端只是单纯将 Msg 写入Redis list 数据结构，CSRedisCore上相关github issue给了我一些启发。
发现自己将CSRedisClient实例化代码写在 .netcore api Controller构造函数，这样每次请求构造Controller时都实例化一次Redis客户端，最终Redis客户端连接数达到最大允许连接值。
依赖注入三种模式： 单例（系统内单一实例，一次性注入）；瞬态（每次请求产生实例并注入）；自定义范围。
有关dotnet apicontroller 以瞬态模式 注入，请查阅链接。
还有一个疑问？ 为什么Redis服务器没有释放空闲的 客户端连接，如果空闲连接被释放了，即使我写了low代码也不至于如此吧？
查询官方：
By default recent versions of Redis don't close the connection with the client if the client is idle for many seconds: the connection will remain open forever.
However if you don't like this behavior, you can configure a timeout, so that if the client is idle for more than the specified number of seconds, the client connection will be closed.
You can configure this limit via
redis.confor simply usingCONFIG SET timeout <value>.
大致意思是最近的Redis服务端版本 默认不会释放空闲的客户端连接：
# Close the connection after a client is idle for N seconds (0 to disable)
timeout 0
可通过修改Redis配置释放 空闲客户端连接。
我们最佳实践当然不是修改Redis idle timeout 配置，问题核心还是因为我实例化了多客户端，赶紧将CSRedisCore实例化代码移到startup.cs并注册为单例。
大胆求证
info clients命令显示稳定在53个Redis连接。
client list命令显示：172.16.1.3（故障容器）建立了50个客户端连接，编排的另一个容器webapp建立了2个连接，redis-cli命令登录到服务器建立了1个连接。
127.0.0.1:> client list
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=127.0.0.1: fd= name= age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=client
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=lpush
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.4: fd= name=f176f125a4c5 age= idle= flags=P db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.4: fd= name=f176f125a4c5 age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=rpop
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=ping
id= addr=172.16.1.3: fd= name=receiver age= idle= flags=N db= sub= psub= multi=- qbuf= qbuf-free= obl= oll= omem= events=r cmd=pin
client list命令显示连接
那么问题来了，修改之后，receiver容器为什么还稳定建立了50个redis连接？
进一步与CSRedisCore原作者沟通，确定CSRedisCore有预热机制，默认在连接池中预热了５０个连接。
bingo，故障和困惑全部排查清楚。
总结
经此一役，在使用CSRedisCore客户端时， 要深入理解
① Stackexchange.Redis 使用的多路复用连接机制（使用时很容易想到注册到单例），CSRedisCore开源库采用连接池机制，在高并发场景下强烈建议注册为单例， 否则在生产使用中可能会误用在瞬态请求中实例化，导致redis客户端几天之后被占满。
② CSRedisCore会默认建立连接池，预热50个连接， 开发者心里要有数。
额外的方法论： 尽量不要从某度找答案，要学会问问题，并尝试从官方、stackoverflow 、github社区寻求解答，你挖过的坑也许别人早就挖过并踏平过。
------------------------------update 多说两句---------------------------------------------
很多博友说问题在于我没有细看CSRedisCore官方readme（readme推荐使用单例），使用方式上我确实没有做成单例：
③ 一般连接池都会有空闲释放回收机制 （CSRedisCore也是连接池机制），所以当时并没有把 单例放在心上
④ 本次重要知识点：Redis默认并不会释放空闲客户端连接（但是又设置了最大连接数），这也直接促成了本次容器崩溃事故。
嗯，坑是自己挖的。
一次误用CSRedisCore引发的redis故障排除经历的更多相关文章
- 记一次linux Docker网络故障排除经历
背景: 之前做了一个项目,需要在容器内访问宿主机提供的Redis 服务(这是一个比较常见的应用场景哈), 常规方案: ① 主机网络(docker run --network=host): 完全应用 ...
- spark 性能优化 数据倾斜 故障排除
版本:V2.0 第一章 Spark 性能调优 1.1 常规性能调优 1.1.1 常规性能调优一:最优资源配置 Spark性能调优的第一步,就是为任务分配更多的资源,在一定范围 ...
- Sentry 监控 - 私有 Docker Compose 部署与故障排除详解
内容整理自官方开发文档 系列 1 分钟快速使用 Docker 上手最新版 Sentry-CLI - 创建版本 快速使用 Docker 上手 Sentry-CLI - 30 秒上手 Source Map ...
- 理解 OpenStack + Ceph （7）: Ceph 的基本操作和常见故障排除方法
本系列文章会深入研究 Ceph 以及 Ceph 和 OpenStack 的集成: (1)安装和部署 (2)Ceph RBD 接口和工具 (3)Ceph 物理和逻辑结构 (4)Ceph 的基础数据结构 ...
- 细化如何安装LNMP + Zabbix 监控安装文档以及故障排除
1.LNMP所需安装包: 上传如下软件包到/soft目录中 mysql- (centos6. 64位自带)也可根据版本自行挑选,前提你了解这个版本 pcre-8.36.tar.gz nginx-.ta ...
- 第十篇 Replication：故障排除
本篇文章是SQL Server Replication系列的第十篇,详细内容请参考原文. 复制故障排除是一项艰巨的任务.在任何复制设置中,都涉及到很多移动部件,而可用的工具并不总是很容易识别问题.Th ...
- 《DevOps故障排除：Linux服务器运维最佳实践》读书笔记
首先,这本书是Linux.CN赠送的,多谢啦~ http://linux.cn/thread-12733-1-1.html http://linux.cn/thread-12754-1-1.html ...
- 利用Ring Buffer在SQL Server 2008中进行连接故障排除
原文:利用Ring Buffer在SQL Server 2008中进行连接故障排除 出自:http://blogs.msdn.com/b/apgcdsd/archive/2011/11/21/ring ...
- JVMTI 中间JNI系列功能，线程安全和故障排除技巧
JVMTI 中间JNI系列功能,线程安全和故障排除技巧 jni functions 在使用 JVMTI 的过程中,有一大系列的函数是在 JVMTI 的文档中 没有提及的,但在实际使用却是很实用的. 这 ...
随机推荐
- SonarQube系列二、分析dotnet core/C#代码
[前言] 本系列主要讲述sonarqube的安装部署以及如何集成jenkins自动化分析.netcore项目.目录如下: SonarQube系列一.Linux安装与部署 SonarQube系列二.分析 ...
- SAP Special Fields in FAGLL03 transaction
https://wiki.scn.sap.com/wiki/display/ERPFI/Special+Fields+in+FAGLL03+transaction https://wiki.scn.s ...
- Mysql5.6对时间的处理精度问题
在业务处理需要使用new Date()来更新时间类型的字段时,数据库会对时间类型进行四舍五入处理,如果new Date()的更新时间与原时间间隔太短,数据库进行四舍五入之后,认为值没有变化,从而不更新 ...
- Java网络编程 -- BIO 阻塞式网络编程
阻塞IO的含义 阻塞(blocking)IO :阻塞是指结果返回之前,线程会被挂起,函数只有在得到结果之后(或超时)才会返回 非阻塞(non-blocking)IO :非阻塞和阻塞的概念相对应,指在不 ...
- 40 篇原创干货，带你进入 Spring Boot 殿堂！
两个月前,松哥总结过一次已经完成的 Spring Boot 教程,当时感受到了小伙伴们巨大的热情. 两个月过去了,松哥的 Spring Boot 教程又更新了不少,为了方便小伙伴们查找,这里再给大家做 ...
- PyQt编写Python GUI程序，简易示例
https://blog.csdn.net/qq_41841569/article/details/81014207
- 史上最全面的SignalR系列教程-6、SignalR 实现聊天室
1.概述 通过前面几篇文章对SignalR的详细介绍.我们知道Asp.net SignalR是微软为实现实时通信的一个类库.一般情况下,SignalR会使用JavaScript的长轮询(long po ...
- Lock同步锁
Lock同步锁 一.前言 在Java 5.0 之前,协调共享对象的访问时可以使用的机制只有synchronized 和volatile .Java 5.0 后增加了一些新的机制,但并不是一种替代内置锁 ...
- 分清<url-pattern>/</url-pattern>与<url-pattern>/*</url-pattern>的不同
在写springMVC配置web.xml的时候会碰到下面有时候写/,有的时候又写/: 那么这两者有什么区别呢?我现在进行一些讲解: 1.当配置<url-pattern>/</url- ...
- 【Edu 67】 补题记录
CF1187D. Subarray Sorting 想要把一个数x换到前面,x一定是小一点的值.由于B串是固定的,A串可调整,我们可以遍历B数组,对于B[i],找到对于在A数组的位子pos,判断1-p ...