]]>
1 [2963] 07 Sep 09:15:07.053 * 10 changes in 300 seconds. Saving
2 [2963] 07 Sep 09:15:07.055 * Background saving started by pid 3143
3 [3143] 07 Sep 09:15:07.058 # Failed opening .rdb for saving: Permission denied
4 [2963] 07 Sep 09:15:07.156 # Background saving error
2 [2963] 07 Sep 09:15:07.055 * Background saving started by pid 3143
3 [3143] 07 Sep 09:15:07.058 # Failed opening .rdb for saving: Permission denied
4 [2963] 07 Sep 09:15:07.156 # Background saving error
鏍規嵁鎻愮ず錛屽彲浠ョ湅鍑烘槸鏉冮檺闂銆?br />榪涘叆redis.conf閰嶇疆鏂囦歡銆?br />鎼滅儲dir錛屾壘鍒板涓嬪唴瀹癸細
1 # The working directory.
2 #
3 # The DB will be written inside this directory, with the filename specified
4 # above using the 'dbfilename' configuration directive.
5 #
6 # The Append Only File will also be created inside this directory.
7 #
8 # Note that you must specify a directory here, not a file name.
9 dir ./
2 #
3 # The DB will be written inside this directory, with the filename specified
4 # above using the 'dbfilename' configuration directive.
5 #
6 # The Append Only File will also be created inside this directory.
7 #
8 # Note that you must specify a directory here, not a file name.
9 dir ./
濡傛灉鏄?/琛ㄧず錛氳繍琛宺eides鍛戒護鐨勭洰褰?渚嬪錛?redis_home涓紝鎵ц./bin/redis-server etc/redis.conf鍛戒護錛?/鍒欎唬琛ㄧ殑鏄?redis_home)銆?br />
鏌ョ湅褰撳墠鐢ㄦ埛瀵筪ir鎵閰嶇疆鐨勮礬寰勬槸鍚︽湁鍐欐潈闄愩?br />
璋冩暣鏉冮檺鍚庯紝搴旇鑳界湅鍒板涓嬩俊鎭細
1 [3223] 07 Sep 09:29:57.007 * 10 changes in 300 seconds. Saving
2 [3223] 07 Sep 09:29:57.008 * Background saving started by pid 3270
3 [3270] 07 Sep 09:29:57.028 * DB saved on disk
4 [3270] 07 Sep 09:29:57.029 * RDB: 6 MB of memory used by copy-on-write
5 [3223] 07 Sep 09:29:57.112 * Background saving terminated with success
2 [3223] 07 Sep 09:29:57.008 * Background saving started by pid 3270
3 [3270] 07 Sep 09:29:57.028 * DB saved on disk
4 [3270] 07 Sep 09:29:57.029 * RDB: 6 MB of memory used by copy-on-write
5 [3223] 07 Sep 09:29:57.112 * Background saving terminated with success
琛ㄧず鎴愬姛鍐欏叆紓佺洏鏂囦歡錛屽嵆璇ラ棶棰樿В鍐熾?br />鐜板湪鏌ョ湅dir鎵閰嶇疆鐨勭洰褰曚笅搴旇鏈塪ump.rdb鏂囦歡銆?img src ="http://www.tkk7.com/liuyf8688/aggbug/403801.html" width = "1" height = "1" />
]]>
1 [29446] 07 Sep 08:14:14.162 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
欏轟究鎻愪竴涓嬶細overcommit_memory鐨勪綔鐢ㄣ?br />
overcommit_memory:
This value contains a flag that enables memory overcommitment.
When this flag is 0, the kernel attempts to estimate the amount
of free memory left when userspace requests more memory.
When this flag is 1, the kernel pretends there is always enough
memory until it actually runs out.
When this flag is 2, the kernel uses a "never overcommit"
policy that attempts to prevent any overcommit of memory.
This feature can be very useful because there are a lot of
programs that malloc() huge amounts of memory "just-in-case"
and don't use much of it.
鏄庣櫧浜嗗師鍥狅紝閭ｅ氨鏍規嵁鎻愮ず榪涜淇敼鍚э紒
鏂規硶1錛氬彧褰卞搷鏈
1.楠岃瘉緋葷粺涓璷vercommit_memory鐨勫鹼紝鎵ц濡備笅鍛戒護
]]>Redis瀹夎 http://www.tkk7.com/liuyf8688/articles/403792.html椋庢矙 椋庢矙 Sat, 07 Sep 2013 12:15:00 GMT http://www.tkk7.com/liuyf8688/articles/403792.html http://www.tkk7.com/liuyf8688/comments/403792.html http://www.tkk7.com/liuyf8688/articles/403792.html#Feedback 0 http://www.tkk7.com/liuyf8688/comments/commentRss/403792.html http://www.tkk7.com/liuyf8688/services/trackbacks/403792.html
The default value is 0. (寰堝鏄撹仈鎯沖埌涓婇潰鐨勶細WARNING overcommit_memory is set to 0!)
See Documentation/vm/overcommit-accounting and
security/commoncap.c::cap_vm_enough_memory() for more information.
==============================================================
overcommit_ratio:
When overcommit_memory is set to 2, the committed address
space is not permitted to exceed swap plus this percentage
of physical RAM. See above.
鏄庣櫧浜嗗師鍥狅紝閭ｅ氨鏍規嵁鎻愮ず榪涜淇敼鍚э紒
鏂規硶1錛氬彧褰卞搷鏈
1.楠岃瘉緋葷粺涓璷vercommit_memory鐨勫鹼紝鎵ц濡備笅鍛戒護
sysctl -n vm.overcommit_memory
2.璁劇疆overcommit_memory鐨勫間負1
sysctl -w vm.overcommit_memory=1
3.楠岃瘉緋葷粺涓璷vercommit_memory鐨勫兼槸鍚﹁鏀規垚浜?
閲嶆柊榪愯redis錛岄獙璇佽鍛婃槸鍚︽秷澶?/div>2.璁劇疆overcommit_memory鐨勫間負1
sysctl -w vm.overcommit_memory=1
3.楠岃瘉緋葷粺涓璷vercommit_memory鐨勫兼槸鍚﹁鏀規垚浜?
sysctl -n vm.overcommit_memory
鏂規硶2:(闇閲嶅惎)
1.灝唙m.overcommit_memory = 1娣誨姞鍒?etc/sysctl.conf涓?br />2.閲嶅惎鐢佃剳
鏂規硶2:(闇閲嶅惎)
1.灝唙m.overcommit_memory = 1娣誨姞鍒?etc/sysctl.conf涓?br />2.閲嶅惎鐢佃剳
]]>
Where to find complete Redis documentation?
-------------------------------------------
This README is just a fast "quick start" document. You can find more detailed
documentation at http://redis.io
Building Redis
--------------
Redis can be compiled and used on Linux, OSX, OpenBSD, NetBSD, FreeBSD.
We support big endian and little endian architectures.
It may compile on Solaris derived systems (for instance SmartOS) but our
support for this platform is "best effort" and Redis is not guaranteed to
work as well as in Linux, OSX, and *BSD there.
It is as simple as:
% make
You can run a 32 bit Redis binary using:
% make 32bit
After building Redis is a good idea to test it, using:
% make test
Fixing problems building 32 bit binaries
---------
If after building Redis with a 32 bit target you need to rebuild it
with a 64 bit target, or the other way around, you need to perform a
"make distclean" in the root directory of the Redis distribution.
In case of build errors when trying to build a 32 bit binary of Redis, try
the following steps:
* Install the packages libc6-dev-i386 (also try g++-multilib).
* Try using the following command line instead of "make 32bit":
make CFLAGS="-m32 -march=native" LDFLAGS="-m32"
Allocator
---------
Selecting a non-default memory allocator when building Redis is done by setting
the `MALLOC` environment variable. Redis is compiled and linked against libc
malloc by default, with the exception of jemalloc being the default on Linux
systems. This default was picked because jemalloc has proven to have fewer
fragmentation problems than libc malloc.
To force compiling against libc malloc, use:
% make MALLOC=libc
To compile against jemalloc on Mac OS X systems, use:
% make MALLOC=jemalloc
Verbose build
-------------
Redis will build with a user friendly colorized output by default.
If you want to see a more verbose output use the following:
% make V=1
Running Redis
-------------
To run Redis with the default configuration just type:
% cd src
% ./redis-server
If you want to provide your redis.conf, you have to run it using an additional
parameter (the path of the configuration file):
% cd src
% ./redis-server /path/to/redis.conf
It is possible to alter the Redis configuration passing parameters directly
as options using the command line. Examples:
% ./redis-server --port 9999 --slaveof 127.0.0.1 6379
% ./redis-server /etc/redis/6379.conf --loglevel debug
All the options in redis.conf are also supported as options using the command
line, with exactly the same name.
Playing with Redis
------------------
You can use redis-cli to play with Redis. Start a redis-server instance,
then in another terminal try the following:
% cd src
% ./redis-cli
redis> ping
PONG
redis> set foo bar
OK
redis> get foo
"bar"
redis> incr mycounter
(integer) 1
redis> incr mycounter
(integer) 2
redis>
You can find the list of all the available commands here:
http://redis.io/commands
Installing Redis
-----------------
In order to install Redis binaries into /usr/local/bin just use:
% make install
You can use "make PREFIX=/some/other/directory install" if you wish to use a
different destination.
Make install will just install binaries in your system, but will not configure
init scripts and configuration files in the appropriate place. This is not
needed if you want just to play a bit with Redis, but if you are installing
it the proper way for a production system, we have a script doing this
for Ubuntu and Debian systems:
% cd utils
% ./install_server
The script will ask you a few questions and will setup everything you need
to run Redis properly as a background daemon that will start again on
system reboots.
You'll be able to stop and start Redis using the script named
/etc/init.d/redis_<portnumber>, for instance /etc/init.d/redis_6379.
Code contributions
---
Note: by contributing code to the Redis project in any form, including sending
a pull request via Github, a code fragment or patch via private email or
public discussion groups, you agree to release your code under the terms
of the BSD license that you can find in the COPYING file included in the Redis
source distribution.
Please see the CONTRIBUTING file in this source distribution for more
information.
Enjoy!
]]>