In operation should always remember Redis Redis is single-threaded operation, if there is a time-consuming operation, block other operations.
Start on Thursday night began to nail the group Redis alarm, not a lot, there is a night reported dozens. Data (non-large Key) written Redis failed. Friday start troubleshooting. Personally I think that on the line Friday and Friday is the most accurate of the BUG ~
Development platform .net, using StackExchange.Redis to operate Redis.
API calls on the server returned the following error message:
"ExceptionMessage": "Timeout performing ... I feel this information as an error message when OOM and display the error location and the actual display of error location does not really matter which fortunately also shows an address:. Https: // stackexchange. . github.io/StackExchange.Redis/Timeouts which details may result in overtime because Redis operation, so that you can troubleshoot issues specific points of the cause of timeouts is: List the amount of data in the hundreds of thousands, in deleted consuming relatively long time. blocking other operations.
Faster way is to see through slowlog Redis commands that operate consuming higher. https://redis.io/commands/slowlog
Redis> SLOWLOG the GET . 1 ) . 1 ) (Integer) 12 is # Uniqueness (UNIQUE) log identifier 2 ) (Integer) 1324097834 point command execution time is recorded #, expressed in UNIX timestamp format . 3 ) (Integer) 16 # query execution time, in microseconds . 4 ) . 1 ) " the CONFIG " command executed # arranged in an array of 2 ) " the GET " # full command here is the GET slowlog-log-the CONFIG slower- Within last . 3 ) " slowlog It would help-Within last--log "