超时执行集合{}键,研究所:0,MGR:无效,队列:2,曲= 1,QS = 1,QC = 0,WR = 1/1,在= 0/0 [英] Timeout performing SET {Key}, inst: 0, mgr: Inactive, queue: 2, qu=1, qs=1, qc=0, wr=1/1, in=0/0

查看:1807
本文介绍了超时执行集合{}键,研究所:0,MGR:无效,队列:2,曲= 1,QS = 1,QC = 0,WR = 1/1,在= 0/0的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想保存使用StackExchange.Redis客户端90 KB PDF文件到Azure的Redis的缓存。我已经转换的文件转换成字节数组,并试图用stringSet方法来保存它,并收到错误。

I am trying to save a 90 KB pdf file into Azure Redis Cache using StackExchange.Redis client. I have converted that file into byte array and tried to save it using stringSet method and received error.

code:

字节[]字节= File.ReadAllBytes(ABC.pdf);
cache.StringSet(info.Name,字节); - >这一行抛出异常超时执行集合{}键,研究所:0,MGR:无效,队列:2,曲= 1,QS = 1,QC = 0,WR = 1/1,在= 0/0

byte[] bytes = File.ReadAllBytes("ABC.pdf"); cache.StringSet(info.Name, bytes); --> This Line throws exception "Timeout performing SET {Key}, inst: 0, mgr: Inactive, queue: 2, qu=1, qs=1, qc=0, wr=1/1, in=0/0".

请帮助。

推荐答案

超时执行集合{键},研究所:0,MGR:无效,队列:2,曲= 1,QS = 1,QC = 0,WR = 1/1,在= 0/0
 意味着,它已派出一个请求(QS),还有就是在未发送队列(曲),而没有什么从网络读取另一个请求。有一个活跃的作家意一个未发送没有被忽略。基本上,存在发送和等待响应能回到一个请求

Timeout performing SET {Key}, inst: 0, mgr: Inactive, queue: 2, qu=1, qs=1, qc=0, wr=1/1, in=0/0 means, it has sent one request (qs), there is another request that's in unsent queue (qu), while there is nothing to be read from the network. there is an active writer meaning the one unsent is not being ignored. Basically, there is a request sent and waiting for the response to be back.

几个问题:
 1.您的客户端在同一区域用作缓存运行?从开发框上运行,将推出额外的延迟而导致超时。
 2.你是否经常得到的异常?它是否成功的任何时间?
 3.您也可以联系azurecache@microsoft.com与缓存名称,时间(带有时区)范围内,你看到了超时,如果可能,一个控制台应用程序,这将有助于瑞普问题。

Few questions: 1. Is your client running in the same region as the cache? Running it from your dev box would introduce additional latency and cause timeouts. 2. How often do you get the exception? Does it succeed any time? 3. You can also contact azurecache@microsoft.com with your cache name, time (with time zone) range in which you see the timeouts and if possible a console app that would help to repro the issue.

希望这有助于
 迪帕克

Hope this helps, Deepak

有关错误codeS从这个线程的详细信息:#83
 研究所:在过去的时间片:0命令已经发出
 经理:插座经理正在执行socket.select,这意味着它要求OS,表明有事情做一个插座;基本上是:读者不积极从网络上阅读,因为它不觉得有什么做
 排队:有73总正在进行的操作
 曲:那些6是在未发送队列:它们尚未写入出站网络
 QS:那些已经发送的67和正在等待服务器的响应
 QC:那些0所看到的答复,但尚未被标记为完成,由于等待结束循环
 WR:有一个活跃的作家(意为 - 那些未发送6不会被忽略)
 在:没有活动的读者和零字节可用要在NIC

details about the error codes from this thread: #83 inst: in the last time slice: 0 commands have been issued 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 qu: 6 of those are in unsent queue: they have not yet been written to the outbound network qs: 67 of those have been sent and are awaiting responses from the server qc: 0 of those have seen replies but have not yet been marked as complete due to waiting on the completion loop wr: there is an active writer (meaning - those 6 unsent are not being ignored) in: there are no active readers and zero bytes are available to be read on the NIC

这篇关于超时执行集合{}键,研究所:0,MGR:无效,队列:2,曲= 1,QS = 1,QC = 0,WR = 1/1,在= 0/0的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆