re
/
ledisdb
forked from mirror/ledisdb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update doc

This commit is contained in:
siddontang 2014-09-29 14:11:14 +08:00
parent 99fcee2e58
commit 956a8b4421
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -13,7 +13,7 @@ LedisDB now supports multiple databases as backend to store data, you can test a
+ Supports lua scripting. + Supports lua scripting.
+ Supports expiration and ttl. + Supports expiration and ttl.
+ Supports using redis-cli directly. + Supports using redis-cli directly.
+ Multiple client API supports, including Go, Python, Lua(Openresty), C/C++, Node.js. + Multiple client API support, including Go, Python, Lua(Openresty), C/C++, Node.js.
+ Easy to embed in your own Go application. + Easy to embed in your own Go application.
+ Restful API support, json/bson/msgpack output. + Restful API support, json/bson/msgpack output.
+ Replication to guarantee data safe. + Replication to guarantee data safe.
@ -75,7 +75,7 @@ Create a workspace and checkout ledisdb source
## Choose store database ## Choose store database
LedisDB now supports goleveldb, lmdb, leveldb, rocksdb, boltdb, hyperleveldb. it will choose goleveldb as default to store data if you not set. LedisDB now supports goleveldb, lmdb, leveldb, rocksdb, boltdb, hyperleveldb, memory. it will choose goleveldb as default to store data if you don't set.
Choosing a store database to use is very simple, you have two ways: Choosing a store database to use is very simple, you have two ways:

10
doc/Replication.md
View File

@ -10,7 +10,7 @@ Another implementation influencing me is [Raft](http://raftconsensus.github.io/)
Refer above, I supply a simple solution for LedisDB's replication. Refer above, I supply a simple solution for LedisDB's replication.
## Key word ## Keyword
+ LogID: a monotonically increasing integer for a log + LogID: a monotonically increasing integer for a log
+ FirstLogID: the oldest log id for a server, all the logs before this id have been purged. + FirstLogID: the oldest log id for a server, all the logs before this id have been purged.
@ -62,14 +62,14 @@ You must notice that this feature has a big influence on the performance. Use yo
Using replication is very simple for LedisDB, only using `slaveof` command. Using replication is very simple for LedisDB, only using `slaveof` command.
+ Uses `slaveof host port` to enable replication from master at "host:port". + Use `slaveof host port` to enable replication from master at "host:port".
+ Uses `slaveof no one` to stop replication and changes to master. + Use `slaveof no one` to stop replication and change the slave to master.
If a slave first syncs from a master A, then uses slaveof to sync from master B, it will sync with the LogID = LastLogID + 1. If you want to start over from B, you must first use `slaveof host port restart`. If a slave first syncs from a master A, then uses `slaveof` to sync from master B, it will sync with the LogID = LastLogID + 1. If you want to start over from B, you must use `slaveof host port restart` which will start a full sync first.
## Limitation ## Limitation
+ Replication can not store log less than current LastLogID. + Replication can not store log less than current LastLogID.
+ Cycle replication not support. + Cycle replication is not supported.
+ Master and slave must set `use_replication` to true to support replication. + Master and slave must set `use_replication` to true to support replication.