hackpar / redis

Automatically exported from code.google.com/p/redis
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

diskstore blocks after flushall #556

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What version of Redis you are using, in what kind of Operating System?

redis_version:2.9.0
redis_git_sha1:521ddcce
redis_git_dirty:0
arch_bits:64
unstable branch

What is the problem you are experiencing?

After flushall with enabled diskstore the cache_io_queue_len is not empty and 
redis blocks until cache-flush-delay has been reached.

What steps will reproduce the problem?

Configure redis to use diskstore with the following values.

diskstore-enabled yes 
diskstore-path redis.ds
cache-max-memory 500MB
cache-flush-delay 120

Insert 6000 items so you have a huge value in cache_io_queue_len, then run 
flushall. Flushall retuns after a few seconds with ok, diskstore is empty but 
the server is blocking new operations until cache_io_queue_len is zero.

We would expecting that flushall command also flushes the cache_io_queue_len 
and the server is not blocking.

Original issue reported on code.google.com by stefan.m...@wooga.net on 20 May 2011 at 3:24