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 think we should share some exciting results.

In the first phase of the stress test, we let Redis perform various tests on Windows, from 1 days to 16 days, and a simple single-master configuration, to more complex configurations like the one shown, 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 only found a BUG and of course we have fixed it.

These completed tests were migrated to the Windows version based on the Linux version of Redis2.6.8, which completed all of the goals we announced in January, such as supporting 64-bit systems. Our goal is to ensure that developers can confidently use Redis on Windows, including business scenarios where high-quality requirements are required. 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 any app or scenario that Redis developers find appropriate.

Comments more wonderful 1 floor:

I'm glad to see your progress. We like to use Redis in distributed projects, but always run standalone Linux servers or Redis-only virtual machines. Of course, this is not a big deal, depending on the circumstances of the decision.

Good job! (Good work!)

2 Floor:

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

3 Floor:

Redis 2.8.12--I have two versions of Redis-server.exe: one is 32 bits, the other is 64 bits, and when you start these two versions, a RedisQFork.dat file is created, and when I run the 32-bit EXE, the size of this file is ten MB, and The problem is that the RedisQFork.dat file becomes 16GB when you run 64-bit.

So what are some of the ways (such as configuring some parameters) that Redis won't be able to 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 you have to create this file, what can you do to make Redis go to another disk or network (UNC path) to create, such as 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 as rushdeep, that is, in the 64-bit version of 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 set the Redis boot parametersheapdirTo adjust the location of this file. 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 to the eldest boss, know the truth of life should not be confused, so go home to solve this problem, Baidu a search redisqfork, found this article, of course, according to 5 floor of the treatment ideas, this is solved.

I'm hereredis.windows.confFiles in the search "heapdir, and then add a line below the default commented-out content to specify the path to the Redis memory-mapped file (storage mapped files):

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

specific files and directories please specify according to your own disk. My symptoms and circumstances are such that 16GB memory, Windows version 64bit Redis, started Redis after the C-drive  c:\windows\serviceprofiles\networkservice\appdata\local\redis   directory below to generate a 16GB size Redisqfork_8792.dat The file (8792 is the process PID that starts, and the file is automatically deleted if Redis is turned off). Originally in order to save money only on the 64GB solid-state drive, the result 16G a eat down, c disk only 16GB free space, since set to D disk, after restarting, feeling obsessive-compulsive disorder is much better.

# maxheap Specifies the maximum number of heap bytes, such as 10000000# maxheap <bytes># maxmemory Specifies the maximum memory to use, in bytes # maxmemory <bytes>  

Please refer to the instructions in the configuration file for the specific parameters, a search will know. (mainly anchor configuration These two parameters have been wrong, half a day start not up, and so on.)

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 directory: https://github.com/cncounter/translation

Reliable Windows version of Redis