January
1st,
1970
本篇作為筆記用途，紀錄 Redis 參考資料
StackExchange.Redis - Configuration
REF: StackExchange.Redis - Configuration
Redis 命令参考
REF: Redis 命令参考
Error Code 說明
- REF: ASP.NET Thread Pool 與 Redis Timeout Exception
- REF: Investigating timeout exceptions in StackExchange.Redis for Azure Redis Cache
System.TimeoutException: Timeout performing MGET 2728cc84-58ae-406b-8ec8-3f962419f641,
inst: 1,mgr: Inactive, queue: 73, qu=6, qs=67, qc=0, wr=1/1, in=0/0
| Error code | Details | 範例 | 說明 |
|---|---|---|---|
| inst | in the last time slice: 0 commands have been issued | 在最後時脈：已發出 0 個命令 | 最後的時脈發出的命令個數 |
| mgr | the socket manager is performing “socket.select”, which means it is asking the OS to indicate a socket that has something to do; basically: the reader is not actively reading from the network because it doesn’t think there is anything to do | 最後的操作命令 | |
| queue | there are 73 total in-progress operations | 73 個正在排隊中的操作 | 正在排隊中的操作 |
| qu | 6 of those are in unsent queue: they have not yet been written to the outbound network | 6 個未發送的 queue | 未發送的 queue |
| qs | 67 of those have been sent to the server but a response is not yet available. The response could be: Not yet sent by the server sent by the server but not yet processed by the client. | 67 個已發送的 queue | 已發送的 queue |
| qc | 0 of those have seen replies but have not yet been marked as complete due to waiting on the completion loop | 0 個已發送未標記完成的 queue | 已發送未標記完成的 queue |
| wr | there is an active writer (meaning - those 6 unsent are not being ignored) bytes/activewriters | 有 1 個啟用的 writer,(意味著 qu 的工作並沒有被忽略) bytes/activewriters | bytes/activewriters |
| in | there are no active readers and zero bytes are available to be read on the NIC bytes/activereaders | 0 個 reader | bytes/activereaders |
| For more information, please see this link | |||
參考資料：