Could not load branches. Could not load tags. Latest commit. Git stats 5, commits. Failed to load latest commit information. Update issue templates. Jun 22, Nov 8, Update redis-cli help and the script to generate it. Nov 17, Jan 26, Nov 4, Fix typo.
Sep 29, Feb 10, Apr 21, Feb 5, Moreover most of the code is heavily commented and easy to follow. You can find a few shell scripts that are used in order to execute the Redis, Redis Cluster and Redis Sentinel unit tests, which are implemented inside the tests directory.
There are a few more directories but they are not very important for our goals here. We'll focus mostly on src , where the Redis implementation is contained, exploring what there is inside each file. The order in which files are exposed is the logical one to follow in order to disclose different layers of complexity incrementally. Note: lately Redis was refactored quite a bit. Function names and file names have been changed, so you may find that this documentation reflects the unstable branch more closely.
For instance, in Redis 3. However the overall structure is the same. Keep in mind that all the new developments and pull requests should be performed against the unstable branch. The simplest way to understand how a program works is to understand the data structures it uses. So we'll start from the main header file of Redis, which is server. All the server configuration and in general all the shared state is defined in a global structure called server , of type struct redisServer.
A few important fields in this structure are:. There are tons of other fields. Most fields are commented directly inside the structure definition. Another important Redis data structure is the one defining a client. In the past it was called redisClient , now just client.
The structure has many fields, here we'll just show the main ones:. As you can see in the client structure above, arguments in a command are described as robj structures.
The following is the full robj structure, which defines a Redis object :. Basically this structure can represent all the basic Redis data types like strings, lists, sets, sorted sets and so forth. The interesting thing is that it has a type field, so that it is possible to know what type a given object has, and a refcount , so that the same object can be referenced in multiple places without allocating it multiple times.
Finally the ptr field points to the actual representation of the object, which might vary even for the same type, depending on the encoding used.
Redis objects are used extensively in the Redis internals, however in order to avoid the overhead of indirect accesses, recently in many places we just use plain dynamic strings not wrapped inside a Redis object. This is the entry point of the Redis server, where the main function is defined.
The following are the most important steps in order to startup the Redis server. Inside server. Redis uses a persistence model based on the fork system call in order to create a process with the same shared memory content of the main Redis process.
This secondary process dumps the content of the memory on disk. This is used by rdb. The implementation inside aof. The call function defined inside server. Certain Redis commands operate on specific data types; others are general. They operate on keys and not on their values specifically. All those generic commands are defined inside db. Moreover db. The most important functions inside db.
The robj structure defining Redis objects was already described. Inside object. Notable functions inside this file:. This is one of the most complex files inside Redis, it is recommended to approach it only after getting a bit familiar with the rest of the code base. In this file there is the implementation of both the master and replica role of Redis. Sign in to comment. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window.
If you want to install MSOpenTech's latest port of Redis, on a Windows server, watched over by a Windows Service, without having to build anything yourself, read on. MSOpenTech's seems to be the only port that is actively trying to keep up with the latest and greatest Redis. They claim it is production-ready, but they haven't exactly packaged it up neatly for installation on a server, especially if you want to run their RedisWatcher service to keep an eye on it, which is recommended.
I tried building RedisWatcher myself per their instructions, but the required Wix Toolset managed to mess up my system pretty good. I won't go into it. Fortunately they've provided all the binaries you need, just not all in one place. So far the RedisWatcher is not carried over to 2. However this should not be affected by the Redis version, and the code in the 2.
0コメント