Reliable Windows version of Redis

Subtitle: Comments more exciting, teach you how to solve the 64-bit Windows version of Redis mania for the C disk problem.

The MS Open tech team recently spent a lot of time testing the latest build of the Windows Redis (available for download at Ms Open Tech Github warehouse). When our test plan is nearing completion, we feel we should share some exciting results.

In the first phase of the stress test, we let Redis perform a variety of tests on windows, from 1 days to 16 days, as well as a simple single-master configuration, to a more complex configuration as seen, including 1 master and 4 replicas. You can see the overall test strategy and configuration used on our wiki page.

The test results are exciting-we just found a BUG and of course we've fixed it.

These completed tests were migrated to Windows based on the Linux version of Redis2.6.8, which completed all of the goals we announced in January, such as support for 64-bit systems.

Our goal is to ensure that developers have the confidence to use Redis on Windows, including business scenarios with high requirements for sex. We plan to continue testing in more "demanding" scenarios to make sure we haven't missed anything.

If you have any comments or suggestions on business scenarios and test plans/strategies, be sure to tell the authors.

We are happy to use the casual app or scenario that Redis developers find appropriate.

Comments more wonderful 1 floor:

I'm very glad to see your progress. We like to use Redis in distributed projects, but always execute standalone Linux servers or Redis-dedicated virtual machines.

Of course, this is not a big deal, according to the details of the decision.

Good job! (Good work!)

2 Floor:

Good work! Doing development on Windows or simply testing is really good.

3 Floor:

Redis 2.8.12--I have two version number of Redis-server.exe: one is 32 bits, and the other is 64 bit, when you start these two version numbers will create a RedisQFork.dat file, when I execute the 32-bit EXE, the size of this file is 500 MB, and the RedisQFork.dat file becomes 16GB when the 64-bit is executed, which is where the problem lies.

Is there any way (for example, to configure some of the parameters) to let Redis not create this 16GB file?

(By the way my server is Windows 2012, so I want to be able to use 64-bit EXE), back to the problem ... What I'm trying to say is there's no way to make redis do not create this huge file, or if it has to be created, what can be done to make redis go to other disks or networks (UNC paths), for example, where there is a large capacity storage space.

Can you explain what this file is for, by the way?

Thank you!

4 Floor:

I also encountered the same problem with Rushdeep, that is, the 64-bit version number on the Redisqfork_nnnn.dat file occupies 16GB of disk space problem. Is this a bug?

5 Floor:

I ran into the same problem. I'm not sure if the Redisqfork file is smaller, but I'm sure you can adjust the location of the file by setting Redis boot parameters heapdir . For example:redis-server.exe -heapdir D:\redisdata

Anchor notes:

Of course, anchor also encountered this problem for a long time. This evening was   up the boss, know that life should not be blind to the truth, so go home to solve problems, Baidu a search Redisqfork , found this article, of course, according to the 5 floor of the treatment of ideas, this is considered to have conquered.

I redis.windows.conf searched for "" in the file and heapdir then added a line below the default gaze to specify the path to the Redis memory-mapped file (mapped files):

# HEAPDIR Specifies the memory-mapped file path name, cannot be the file name # Heapdir <directory path (absolute or relative) >heapdir d:/temp/redis_heapdir/

Detailed files and folders please specify according to your own disk. My symptoms and situation is this, 16GB memory, Windows version 64bit Redis, after starting Redis on the C drive C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Redis folder below generate a 16GB size Redisqfork_8792.dat file (8792 is the process PID of this start, If you turn off Redis, this file will be deleted on its own initiative. Originally in order to save money just on the 64GB solid-state drive, the result 16G a eat down, c disk just have 16GB free space, since set to D disk, after restarting, feeling obsessive-compulsive disorder is much better.

Of course, anchor is not going to talk about this, but to introduce 2 of the parameters:

# MAXHEAP Specifies the maximum number of heap bytes, for example 10000000# maxheap <bytes># maxmemory Specifies maximum usage memory in bytes # maxmemory <bytes>

for detailed reference, please refer to the instructions in the configuration file, a search will know. (mainly anchor configuration These two parameters have been wrong, half-day start not up, and so on, and so the study is clear again.)

Original link: Redis on windows–stable and reliable

Original Date: 2013-04-22

Translation Date: 2014-11-16

Translator: Anchor: Http://blog.csdn.net/renfufei

Cncounter Translation Articles folder: Https://github.com/cncounter/translation

Reliable Windows version of Redis